[PLUG] How To Remove "Ghost" Files?

[chris (fool) mccraw]

On Fri, Oct 8, 2010 at 08:39, Fred James <fredjame at fredjame.cnc.net> wrote:
>
> As mentioned in a post by Ewan, it may be something that needs the
> application of 'fsck', in which case the procedure above may get ride of
> th file(s), but not the problem?

+1 for all of this.

so, make sure you check dmesg before the reboot to see if there are
any hard drive errors being logged, check its SMART status (if it
supports that), and pat yourself on the back for making backups (where
you can also see if there were once files there that got lost, in case
fsck doesn't stick anything in /lost+found)

other than FS corruption (which has manifested like that several times
in my life), i have seem such a corrupted directory listing one other
time...on a CIFS remote file system's mount point, which would only
clear up with a reboot, though i could successfully remount the FS on
another mount point.  accessing the corrupted one would leave a
process stuck in disk wait state.

luck++;