On Thu, 5 Jul 2012, Russell Coker <russell@coker.com.au> wrote:
Anyway I moved that system to btrfs and since then I've got a couple of corrupted files. Both files were from Debian packages so the --reinstall option to apt-get fixed that.
It seems that when a file on disk has a checksum mismatch for all copies you get ESTALE as well as messages on the system console like the following:
[ 6747.164889] btrfs: corrupt leaf, bad key order: block=1116618752,root=1, slot=0
Sometimes you solve a problem once, think it's solved properly, post to a list, and then discover you can't reproduce it. The second corrupt file gives the following: # ls -al /var/lib/dpkg/info/ed.md5sums ls: cannot access /var/lib/dpkg/info/ed.md5sums: Stale NFS file handle # rm -f /var/lib/dpkg/info/ed.md5sums rm: cannot remove `/var/lib/dpkg/info/ed.md5sums': Stale NFS file handle # unlink /var/lib/dpkg/info/ed.md5sums unlink: cannot unlink `/var/lib/dpkg/info/ed.md5sums': Stale NFS file handle This seems a bit bogus. There's no reason why an rm or unlink should fail if the corruption only affects one file. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/