I'd gladly run your tests but I executed my overkill solution prior to
seeing your reply. I should have shown a touch more patience.
Fortunately, it appears to have worked.
On 03/28/2017 11:43 AM, Ken D'Ambrosio wrote:
Hrm. You did an fsck and reboot, and yet you still get a "stale file
handle"? That's... annoying. I don't think I've ever bumped into
quite that situation before. While your potential solution --
backup, reformat, restore -- sounds like overkill, I'm afraid I don't
have anything else, other, possibly, than "Ignore it." Which is
probably sub-optimal, as it might cause issues with things that scan
the hierarchy. I'd be interested in what the output of this is:
strace -s 1024 -f -o /tmp/rm.log rm -- ?
(Feel free to replace "rm -- ?" with whatever it is that throws the
stale file handle error...)
I'd also be interested in whether or not 'dmesg' has anything of note.
-Ken
If there's no way to nuke the file does the following make sense?
1) Copy the partition containing the problem file to a blank
partition, omitting the partition containing the problem file.
2) Reformat the problem partition.
3) Copy the created partition to the reformatted partition.
