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. NFS <v4 clients refer to file by a file handle composed of filesystem id and inode number. Maybe a change in there? Anyway, to find the real error message its necessary to try to delete the files on the server. Cause even if there is a real BTRFS issue, the NFS client likely won´t report helpful error messages. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
