lost+found, fsck logs and what not

[pmcmicha]

I just had a slice go nuts over the weekend and the fsck is about 16 - 17 times the size it should be and the lost+found directory under this slice is filled with a bunch of files. No crash dump was logged.

How can I go about trying to track down what happened on this system?

Thanks in advance.

 

[pcunix]

Not knowing what OS version you are running or what filesystem type you used, it's hard to say much.

An HTFS filesystem on a current 5.0.[4-6] properly patched is very hard to damage, so if that were the situation I would guess hardware problems or a root (user/program) scribbling where it should not have.

But a 3.2v4.2 on EAFS is fairly easy to muck up pretty thoroughly if it was very busy when the system went down.

Did anyone notice a panic? Tony Lawrence
SCO Unix/Linux Resources

http://pcunix.com

tony@pcunix.com

 

[pmcmicha]

OS: SCO Unixware 7.1.1
FS: vxfs

No panics were reported on this box. I guess my real question is, can I use the /lost+found directory to track down what went wrong?

Thanks.

 

[pcunix]

No. You can use lost+found to restore files that were disconnected from their directory, but that isn't going to tell you a thing about why this happened.

Tony Lawrence
SCO Unix/Linux Resources

http://pcunix.com

tony@pcunix.com