On Tue, 11 Apr 2000, Ed Carp wrote:
> The problem with this approach is, if you're working with systems that
> are up 24x7, to *not* have the ability to automatically detect a bad
> block, copy the data to another block, then mark that block as bad is a
> real pain at best and completely unacceptable at worst. One of my
> clients is using Linux in a network communications controller (SONET/ATM
> backplane) and this sort of thing is going to raise the pain level
> around here as soon as someone realizes that badblocks aren't taken case of.
>
> On the bright side, if we have to do the code in-house, I'm pretty sure
> I can convince them to GPL the code such that the entire community can
> benefit from our work. :)
WOOHOO, someone has followed my brain trace.......
I want access........I have taken enough heat because of possible FS
corruptions resulting from hardware that is aged, that I want a bullet
proof recovery.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
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