From: Brad Langhorst <brad@langhorst.com>
To: linux-kernel@vger.kernel.org
Subject: first one disk drops our of raid, then the other - I/O error on same sector. raid bug?
Date: Fri, 01 Jun 2007 20:43:08 -0400 [thread overview]
Message-ID: <1180744988.6830.183.camel@upup> (raw)
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
May 30 12:58:00 bitc kernel: SEQADDR == 0x16c
May 30 12:58:00 bitc kernel: sd 0:0:1:0: SCSI error: return code =
0x00010000
May 30 12:58:00 bitc kernel: end_request: I/O error, dev sdb, sector
287322317
May 30 12:58:00 bitc kernel: raid1: Disk failure on sdb2, disabling
device.
May 30 12:58:00 bitc kernel: ^IOperation continuing on 1 devices
May 30 12:58:01 bitc kernel: sd 0:0:1:0: SCSI error: return code =
0x00010000
May 30 12:58:01 bitc kernel: end_request: I/O error, dev sdb, sector
284758725
May 30 12:58:01 bitc kernel: RAID1 conf printout:
May 30 12:58:01 bitc kernel: --- wd:1 rd:2
May 30 12:58:01 bitc kernel: disk 0, wo:0, o:1, dev:sda2
May 30 12:58:01 bitc kernel: disk 1, wo:1, o:0, dev:sdb2
May 30 12:58:01 bitc kernel: RAID1 conf printout:
May 30 12:58:01 bitc kernel: --- wd:1 rd:2
May 30 12:58:01 bitc kernel: disk 0, wo:0, o:1, dev:sda2
I can add /dev/sdb back
May 30 17:14:17 bitc kernel: md: md1: sync done.
May 30 17:14:17 bitc kernel: RAID1 conf printout:
May 30 17:14:17 bitc kernel: --- wd:2 rd:2
May 30 17:14:17 bitc kernel: disk 0, wo:0, o:1, dev:sda2
May 30 17:14:17 bitc kernel: disk 1, wo:0, o:1, dev:sdb2
thenk /dev/sda fell out!
May 31 02:37:06 bitc kernel: (scsi0:A:0:0): Unexpected busfree in
Command phase
May 31 02:37:06 bitc kernel: SEQADDR == 0x16c
May 31 02:37:06 bitc kernel: sd 0:0:0:0: SCSI error: return code =
0x00010000
May 31 02:37:06 bitc kernel: end_request: I/O error, dev sda, sector
287322317
May 31 02:37:06 bitc kernel: raid1: Disk failure on sda2, disabling
device.
May 31 02:37:06 bitc kernel: ^IOperation continuing on 1 devices
May 31 02:37:06 bitc kernel: sd 0:0:0:0: SCSI error: return code =
0x00010000
May 31 02:37:06 bitc kernel: end_request: I/O error, dev sda, sector
276325445
May 31 02:37:06 bitc kernel: RAID1 conf printout:
May 31 02:37:06 bitc kernel: --- wd:1 rd:2
May 31 02:37:06 bitc kernel: disk 0, wo:1, o:0, dev:sda2
May 31 02:37:06 bitc kernel: disk 1, wo:0, o:1, dev:sdb2
May 31 02:37:06 bitc kernel: RAID1 conf printout:
May 31 02:37:06 bitc kernel: --- wd:1 rd:2
May 31 02:37:06 bitc kernel: disk 1, wo:0, o:1, dev:sdb2
Note that the first error is at the same sector for both disks
287322317(sda) = 287322317(sdb)
but the second one is at a different spot
276325445(sda) != 284758725(sbd)
it seems unlikely that both disks have exactly the same bad sector
Maybe a disk is failing, but smart doesn't show a big difference in ECC
errors between the two disks. Seems wrong that the kernel raid should
first drop one disk, then the other if one disk is really failing.
Is this a bug?
Brad
next reply other threads:[~2007-06-02 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 0:43 Brad Langhorst [this message]
2007-06-02 2:24 ` first one disk drops our of raid, then the other - I/O error on same sector. raid bug? Neil Brown
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=1180744988.6830.183.camel@upup \
--to=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.