From: Johan Groth <johan.groth@linux-grotto.org.uk>
To: Mark Lord <lkml@rtr.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scsi errors with Megaraid 300-8x
Date: Wed, 23 Aug 2006 16:42:20 +0100 [thread overview]
Message-ID: <44EC775C.7040003@linux-grotto.org.uk> (raw)
In-Reply-To: <44EC73D2.9090302@rtr.ca>
Mark Lord wrote:
> Johan Groth wrote:
[snip]
> Basically, given an I/O request for 200 sectors, with a bad sector
> in the middle at number 100, what SCSI will often do is fail sectors
> number 1 through 100, one at a time, retrying the entire remainder of
> the request after each attempt. This takes hours, and results in no
> data for the first 99 good sectors.
So what you are saying is that after the move to a new box and a new
mobo a sector has gone bad on that raid slice? Weird, as I was very
careful this those drives when I moved them.
I mean, the raid controller is the same, the cpus are the same, just
more of them, the pci-x bus the same so I didn't expect any problems at
all.
I was also under the impression that SATA raid controllers work like
SCSI raid controllers in the way that if a bad sector is encountered the
controller moves what it can and the mark the sector as bad. I might be
very wrong about that, though.
However, if I have a bad sector I would like to have that one marked as
bad so the kernel never tries to read it again. Any suggestions how I do
that. I assume I have to boot something like Knoppix as sda is my system
disk.
Regards,
Johan
next prev parent reply other threads:[~2006-08-23 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 14:45 Scsi errors with Megaraid 300-8x Johan Groth
2006-08-23 15:27 ` Mark Lord
2006-08-23 15:42 ` Johan Groth [this message]
2006-08-23 15:45 ` Justin Piszcz
2006-08-23 15:48 ` Johan Groth
2006-08-23 15:53 ` Justin Piszcz
2006-08-23 15:57 ` Johan Groth
2006-08-23 15:59 ` Justin Piszcz
2006-08-24 14:48 ` Mark Lord
2006-08-24 15:09 ` Johan Groth
2006-08-24 16:57 ` Mark Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44EC775C.7040003@linux-grotto.org.uk \
--to=johan.groth@linux-grotto.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox