From: Martin Steigerwald <Martin@lichtvoll.de>
To: "Frédéric COIFFIER" <frederic.coiffier@free.fr>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How to recover uncorrectable errors ?
Date: Thu, 21 Mar 2013 14:27:08 +0100 [thread overview]
Message-ID: <201303211427.09220.Martin@lichtvoll.de> (raw)
In-Reply-To: <1380005.JyAIHqx6kZ@athlonxp>
Am Donnerstag, 21. März 2013 schrieb Frédéric COIFFIER:
> Hi Martin,
>
> Le mercredi 20 mars 2013 19:59:54 Martin Steigerwald a écrit :
> > Am Mittwoch, 20. März 2013 schrieb Frédéric COIFFIER:
> > > > But I really think BTRFS displays the filename affected meanwhile. So
> > > > maybe if it does not, its some metadata being affected? So output of btrfsck
> > > > hints at that and that you can´t remove the file does as well. What happens
> > > > if you try to remove the file? Do you get an input/output error or
> > > > something like that?
> > >
> > > # rm -rf *
> > > rm: cannot remove 'drivers/misc/lis3lv02d/lis3lv02d.c': Stale NFS file handle
> > > rm: cannot remove 'drivers/misc/lis3lv02d/lis3lv02d.c': Stale NFS file handle
> > > rm: cannot remove 'drivers/misc/lis3lv02d/lis3lv02d.c': Stale NFS file handle
> > > rm: cannot remove 'drivers/misc/lis3lv02d/lis3lv02d.c': Stale NFS file handle
> > > rm: cannot remove 'drivers/misc/lis3lv02d/lis3lv02d.c': Stale NFS file handle
> > > rm: cannot remove 'drivers/misc/lis3lv02d/lis3lv02d.c': Stale NFS file handle
> > > rm: cannot remove 'drivers/misc/lis3lv02d/lis3lv02d.c': Stale NFS file handle
> > > rm: cannot remove 'drivers/misc/lis3lv02d/lis3lv02d.c': Stale NFS file handle
> > > ...
> >
> > You are trying to remove the files from an NFS client. Stale NFS file
> > handle just means that the NFS handle is no longer valid.
>
> Absolutely not. I'm not using NFS and I try to remove the files locally.
> It seems that btrfs returns a strange ESTALE errno...
>
> grep -rsn ESTALE fs/btrfs/
> fs/btrfs/inode.c:2412: if (ret && ret != -ESTALE)
> fs/btrfs/inode.c:2415: if (ret == -ESTALE && root == root->fs_info->tree_root) {
> fs/btrfs/inode.c:2451: if (ret == -ESTALE) {
> fs/btrfs/inode.c:4273: inode = ERR_PTR(-ESTALE);
> fs/btrfs/export.c:71: return ERR_PTR(-ESTALE);
> fs/btrfs/export.c:104: return ERR_PTR(-ESTALE);
>
> This error seems to be common (even if I can't see any recent reports) :
> http://www.google.fr/search?q=btrfs+Stale+NFS+file+handle
Thanks for notice. Well I thought one can take the error message literally.
I only ever saw it with NFS and its also NFS in the error message. I think
the error message is at least misleading.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-03-21 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 8:54 How to recover uncorrectable errors ? Frédéric COIFFIER
2013-03-13 8:10 ` Frédéric COIFFIER
2013-03-16 18:16 ` Martin Steigerwald
2013-03-20 13:33 ` Frédéric COIFFIER
2013-03-20 18:19 ` Chris Murphy
2013-03-20 19:24 ` Roman Mamedov
2013-03-20 20:17 ` Chris Murphy
2013-03-21 8:57 ` Frédéric COIFFIER
2013-03-21 15:09 ` Chris Murphy
2013-03-20 18:59 ` Martin Steigerwald
2013-03-20 19:06 ` cwillu
2013-03-21 8:36 ` Frédéric COIFFIER
2013-03-21 13:27 ` Martin Steigerwald [this message]
2013-03-16 18:19 ` Martin Steigerwald
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=201303211427.09220.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=frederic.coiffier@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).