ext2_free_blocks (fwd)

[tytso en mit.edu]

   Date:   Wed, 19 Jan 2000 05:29:21 +0100 (CET)
   From: Andrea Arcangeli <andrea en suse.de>

   On Wed, 19 Jan 2000 tytso en MIT.EDU wrote:

   >[..]  Since fsck -f didn't find any problems, it was probably your
   >hardware hiccuping and returning the wrong block when ext2 tried to read
   >in an indirect block. [..]

   The corrupted metadata block is been freed before fsck had a chance to run
   and once the metadata block become an unused block all returned fine.

How do you know that?  It's a plausible scenario, but only if someone
deleted the file containing the bad indrect block before running fsck.

						- Ted

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo en vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/