On Sep 1,  2:54pm, [email protected] (Paul Ripke) wrote:
-- Subject: Re: Unallocated inode

| Running a second fsck pass comes up clean. What surprises me is that my
| machine has been up ~100 days... I find it hard to believe that a power
| loss or similar unclean shutdown would generate filesystem corruption
| that could sit silent for that long before suddenly emerging.

Great :-)
With the size of the disks and filesystems these days you can end up not
touch large portions of them for a long time. As to why you did crash
when touch them, you were lucking. Finally this is probably a bug in
WAPBL because it is supposed to maintain metadata file system integrity,
but in this case it did not?

cristos

Reply via email to