On Tue, 10 Oct 2006 13:47:56 -0400 Doug Ledford wrote: [...] > So, like my original email said, fsck has no business reading any block > that hasn't been written to either by the install or since the install > when the filesystem was filled up more. It certainly does *not* read > blocks just for the fun of it, nor does it rely on anything the > filesystem didn't specifically write. There are fsck implementations which read potentially unwritten blocks. E.g., reiserfsck --rebuild-tree reads every block on the device, finds anything which looks like a tree block and tries to do something with it. This procedure sometimes recovers files which were deleted, and if an uncompressed image of a reiserfs v3 filesystem was stored in a file on reiserfs, it can confuse reiserfsck badly...
Attachment:
pgpiZrhvO0jMn.pgp
Description: PGP signature
