[4712] in linux-scsi channel archive
Re: medium errors
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Fri Sep 18 19:44:40 1998
Date: Fri, 18 Sep 1998 16:50:37 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Dan Hollis <goemon@sasami.anime.net>
Cc: Jon Lewis <jlewis@inorganic5.fdt.net>,
Linux SCSI Mailing List <linux-scsi@vger.rutgers.edu>
In-Reply-To: Dan Hollis's message of Thu, 17 Sep 1998 20:25:12 -0700 (PDT),
<Pine.LNX.3.96.980917202312.16743A-100000@sasami.anime.net>
Date: Thu, 17 Sep 1998 20:25:12 -0700 (PDT)
From: Dan Hollis <goemon@sasami.anime.net>
On Thu, 17 Sep 1998, Jon Lewis wrote:
> I'm burning in some Micropolis 1991's and of course one has to be giving
> me a hard time. I have ARRE and AWRE enabled, so this shouldn't be
> happening. My questions are...does the fact that these read errors
> happened mean that these sectors have been spared out? If not, and I want
> to try to keep using this disk, can I feed the sector numbers to e2fsck
> and spare these sectors out? If so, do I use the first sector numbers or
> the absolute sectors?
FWIW I get the exact same errors under various other scsi disks. Telling
ext2 to map them out as bad doesn't seem to prevent it from still hitting
them. No idea why. I don't think ive ever had ext2 badblock mapping work
correctly on any drives -- IDE or SCSI.
You have to enter logical *block* numbers --- not sector numbers. If
you entered sector numbers then ext2 will map out the wrong blocks....
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
