From: Chris Hoffmann <chrmhoffmann@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: stale NFS file handle and corrupted btrfs
Date: Sat, 20 Apr 2013 14:41:07 +0200 [thread overview]
Message-ID: <51728CE3.9040804@gmail.com> (raw)
Hi,
I have experienced an error message about stale NFS files when looking
into a directory.
ls -la manpages-dev.md5sums
ls: cannot access manpages-dev.md5sums: Stale NFS file handle
root@c3po:/media/revo/@/var/lib/dpkg/info# rm manpages-dev.md5sums
rm: cannot remove ‘manpages-dev.md5sums’: Stale NFS file handle
Running btrfsck I see:
btrfsck --repair /dev/revo/root
enabling repair mode
checking extents
checking fs roots
root 256 inode 117209 errors 2001
unresolved ref dir 11094 index 2862 namelen 20 name
manpages-dev.md5sums filetype 1 error 4
root 319 inode 117209 errors 2001
unresolved ref dir 11094 index 2862 namelen 20 name
manpages-dev.md5sums filetype 1 error 4
root 320 inode 117209 errors 2001
unresolved ref dir 11094 index 2862 namelen 20 name
manpages-dev.md5sums filetype 1 error 4
found 28530659328 bytes used err is 0
total csum bytes: 27246928
total tree bytes: 629264384
total fs tree bytes: 552144896
btree space waste bytes: 160285807
file data blocks allocated: 57135325184
referenced 28486983680
Btrfs v0.20-rc1
Scrubbing and btrfsck do not fix the issue.
I tried with 3.9.0rc6 and otherwise with 3.8.8 (and 3.8.0-19-generic
#29-Ubuntu)
I have uploaded the btrfs-image to
http://ubuntuone.com/3tIHcUdfGEdmrSY1oxGCL3
The drive is an 64GB crucial M4 SSD. Smartinfo can be found here:
http://pastebin.com/raw.php?i=BJvcB31H
Any help appreciated.
Rgds,
Chris
reply other threads:[~2013-04-20 12:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51728CE3.9040804@gmail.com \
--to=chrmhoffmann@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox