Re: ext2_free_blocks (fwd)

From: Andrea Arcangeli (andrea@suse.de)
Date: Thu Jan 20 2000 - 10:11:06 EST


On Thu, 20 Jan 2000, Rogier Wolff wrote:

>But more importantly, you run the chance that the wrong block, somehow
>marked dirty isn't written back to the drive....

In this case the wrong block is probably been bforgotten in some msec
after he seen the error message. Rebooting immediatly may avoid the
superblock/direntry/inode on-disk update so then fsck may reack the wrong
block and notice the corruption. But in this case allowing fsck to reach
the wrong block won't make any difference (but at least then you'll know
the wrong block was wrong as well on-disk and not only in-memory :).

Andrea

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



This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:23 EST