On Mon, 24 Sep 2001, Alan Cox wrote:
> > > better. Decent write caching on IDE devices (like the 2meg buffer on the IBM)
> > > can completely hide this issue.
> > Decent write caching on IDE devices can eat your whole file system.
> YM bad write caching 8)
Well, drives do reorder their cache flushes, otherwise, they don't need
> > Turn it off (I have no idea of internals, but I presume it'll still be a
> > write-through cache, so reading back will still be served from the
> > buffer). Do hdparm -W0 /dev/hd[a-h].
> You can't turn it off and on many drives you can't flush the cache either
> the operation is not implemented.
Those drives should be blacklisted and rejected as soon as someone tries
to mount those pieces rw. Either the drive can make guarantees when a
write to permanent storage has COMPLETED (either by switching off the
cache or by a flush operation) or it belongs ripped out of the boxes and
stuffed down the throat of the idiot who built it.
-- Matthias Andree
"Those who give up essential liberties for temporary safety deserve neither liberty nor safety." - Benjamin Franklin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 30 2001 - 21:00:23 EST