> It is always the same inode-- When fscking, inode 818763 is always
> deleted with zero dtime.  What does this show? 

This could just be a temporary file that some daemon has opened and unlinked.  
When the system crashes, the one reference to that file (the process) has 
disappeared, so fsck sees an unreferenced file and has to clean it up.

                                Jeff



************
[EMAIL PROTECTED]   http://www.linuxchix.org

Reply via email to