From: Neil Brown <neilb@suse.de>
To: Brad Langhorst <brad@langhorst.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: first one disk drops our of raid, then the other - I/O error on same sector. raid bug?
Date: Sat, 2 Jun 2007 12:24:02 +1000 [thread overview]
Message-ID: <18016.54466.838932.490284@notabene.brown> (raw)
In-Reply-To: message from Brad Langhorst on Friday June 1
On Friday June 1, brad@langhorst.com wrote:
> This is a debian stable system in production. Kernel 2.6.18.
> I upgraded the kernel from 2.6.8 to 2.6.18 about 2 weeks ago and saw no
> problems until today.
>
>
> May 30 12:58:00 bitc kernel: (scsi0:A:1:0): Unexpected busfree in
> Command phase
This error is not indicative of drive problems, but rather of
buss/controller problems.
The fact that identical problems hit both devices support this. I
would suggest that you check all cable connections and re-seat the
SCSI card (if it is a separate card). If the problem persists, look
at replacing hardware.
NeilBrown
prev parent reply other threads:[~2007-06-02 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 0:43 first one disk drops our of raid, then the other - I/O error on same sector. raid bug? Brad Langhorst
2007-06-02 2:24 ` Neil Brown [this message]
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=18016.54466.838932.490284@notabene.brown \
--to=neilb@suse.de \
--cc=brad@langhorst.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.