lkml.org 
[lkml]   [2003]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Blockbusting news, results get worse
From
Date
"Norman Diamond" <ndiamond@wta.att.ne.jp> writes:

> 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.

Right. The correct way of sending such a notice is returning I/O error
on read. It's standard and applications support it for years (of course
we can - and currently do - log the error as well).

> 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.

Storing a log entry in system log doesn't tell applications there is
a problem. It's simply unacceptable.
Relocating on write (at filesystem level) - sure, it would be helpful
(possibly as a compile-time option - most IDE drives and things like
RAM disks don't need it).
--
Krzysztof Halasa, B*FH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:58    [W:0.055 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site