[lkml]   [2003]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Blockbusting news, results get worse
    John Bradford pretended to reply to me:

    > > 4. When writing ZEROES to the bad sector, the drive reports SUCCESS.
    > > But it lies. Subsequent attempts to read still fail. Subsequent
    > > writing of zeroes appears to succeed again. Subsequent attempts to read
    > > still fail.
    > > I still have to say, we can't fix Toshiba, and we can avoid Toshiba, but
    > > meanwhile we can fix Linux.
    > How do you suggest we 'fix' 4, above, other than to flush the cache
    > and verify each time a full sector of zeros is written to the disk?

    Number 4 cannot be fixed by Linux. Why do you pervert my writing?

    The refusal to remove a known defective block from ordinary use in the file
    system can be fixed. How many times does this need to be said? Why do you
    pretend that this is not what I have been saying in this entire thread?

    If I understand Hans Reiser's message correctly, this fix has indeed been
    made in ReiserFS version 4. I thank Mr. Reiser. (By the way, I volunteer
    about one day each weekend for testing, and I am hardly in a position to
    contribute funds. Please let's not beggar each other.)

    By the way some participants in this thread have argued that the block
    should not be replaced by zeroes or random garbage without notice. I fully
    agree. The block should be replaced by zeroes or random garbage WITH
    notice. From the point of view of logging it in the system log, it is
    enough to log it once, it doesn't have to be logged over and over again.
    From the point of view of informing the user whose program is running, the
    dd command does an excellent job, but some unknown program was remaining
    silent when I/O errors were originally detected and logged. I still think
    it is better to get that block out of the file system so that when that file
    is rewritten or when other new files get created or extended then they won't
    try to reuse that block. But I've said this enough too. I guess it's time
    to stop beating this dead horse. But anyway Mr. Reiser understood, and I am
    glad, and I thank him.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:58    [W:0.020 / U:5.264 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site