On 21 April 2003 12:35, John Bradford wrote:
> > > Modern disks generally do this kind of thing themselves. By the
> > > time
> >
> > ^^^^^^^^^^^^
> > How many times does Stephan need to say it? 'Generally do'
> > is not enough, because it means 'sometimes they dont'.
>
> OK, _ALL_ modern disks do.
>
> Name an IDE or SCSI disk on sale today that doesn't retry on write
> failiure. Forget I said 'Generally do'.
I don't know about drives currently on sale, but I think
it is possible that some Flash or DRAM-based IDE pseudo-disks
do not have extensive sector remapping features. They can just
do ECC thing and error out.
Also if disk just runs out of spare sectors, it has no other
option other than just report failure, right? (Oh,
of course it can decide to execute 'my firmware is buggy'
option instead ;)
But.
The disk, which I hold in my hand *right now*, namely:
WD Caviar 21200
MDL: WDAC21200-00H
P/N: 99-004211-000
CCC: E3 2 APR 97 S
DCM: AFAAYAW
WD S/N: WT342 251 1943
does have some bad sectors and otherwise performs satisfactorily.
It's my 'big diskette'. So, if I decide to write some MP3s
on it and carry 'em home, and it will suddenly struck a new bad
sector...
Why in hell should I see my fs remounted RO?
Why do I have to read entire disk to my main disk,
recreate the fs with new badblock map, write back everything,
and retry writing MP3???
I prefer a big fat ugly kernel printk (KERN_ERR) across my console
and all the logs: "ext3fs: write error at sector #NNNN. Marking as bad.
Your disk may be failing!"
What's wrong with me?
-- vda - 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/
This archive was generated by hypermail 2b29 : Wed Apr 23 2003 - 22:00:28 EST