Theodore Y. Ts'o (tytso@MIT.EDU) writes:
> It's one thing if the bad block is in a file data block; there, you can
> relocate the data to another block, assuming you can still read the
> block by the time you find you have a disk error. It's quite another if
> the disk failure happens in a critical piece of the filesystem metadata.
>
> The real right solution to this problem, if you have this kind of
> reliability, is to either use disks that do badblock sparing at a
> low-level, or (better yet) to use RAID. If you have this kind of
> reliability consideration that's what you should really be doing.
> Or, if you using Linux in a somewhat embedded system (such as a network
> communications controller), then perhaps you should be booting off of
> flash ROM, and then keeping temporary files on a RAM disk.
I'm not suggesting that the kernel do everything for me, but it'd be nice. ;)
I suppose that monitoring /var/log/messages will have to be enough ;)
-
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 : Sat Apr 15 2000 - 21:00:17 EST