Re: [gentoo-user] forcing file removal, fails with ESTALE

[Iain Buchanan <iaindb@netspace.net.au>]

Andrey Vul wrote:
> On Thu, Nov 20, 2008 at 19:15, Iain Buchanan<iaindb@netspace.net.au>  wrote:
>> Qian Qiao wrote:
>>> On Thu, Nov 20, 2008 at 18:13, Andrey Vul<andrey.vul@gmail.com>   wrote:
>>>> I'm trying to remove a file, yet it fails with ESTALE ("Stale NFS file
>>>> handle"). I'm thinking that this is due to a corrupt inode but fsck
>>>> fails to fix it.

snip

>>> It's just a stale handle, i.e., some process opened the file, but the
>>> file is then deleted, moved or renamed by another process.
>>>
>>> If you know what process is holding the handle of the non-existent
>>> file, restart it, if not, re-mount the file system.
 >>>
>> `umount -l` might help you there.
 >>
> Umount -l fixes inconsistent inodes / directory entries?
> I thought only fsck -f could do that.

no, but it does help you unmount a file system if a process is holding a 
file open, but you don't know which one, as per the suggestion I replied 
to "remount the file system" :)

-- 
Iain Buchanan <iaindb at netspace dot net dot au>

<sj7trunks> so after updating glibc i just need to emerge -eup
<carpaski> -e == truck
<carpaski> -u == small cat
<carpaski> -eu == truck running over small cat