From: Robert L Mathews <lists@tigertech.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 1 failure on single disk causes disk subsystem to lock up
Date: Mon, 31 Mar 2008 10:27:46 -0700 [thread overview]
Message-ID: <47F11F12.7010309@tigertech.com> (raw)
In-Reply-To: <47F0281F.1070404@harddata.com>
Maurice Hilarius wrote:
> How old are the controllers/motherboards?
>
> Is the controller ON the motherboard?
They're SuperMicro 6013A-T servers with this motherboard:
http://www.supermicro.com/products/motherboard/Xeon/E7501/X5DPA-TGM+.cfm
It appears to use an "Adaptec ICH5R SATA controller" on the motherboard
(there's no separate SATA card or anything like that). Although that
controller apparently has an optional RAID feature, I'm not using it;
it's just in standard JBOD mode.
> What you describe sounds suspiciously like an IDE to SATA bridge chip.
> Or, in other words, ATA behaviour.
Here's part of the output from "lshw" on one of these machines:
*-ide:1
description: IDE interface
product: 82801EB (ICH5) Serial ATA 150 Storage Controller
vendor: Intel Corp.
physical id: 1f.2
bus info: pci@00:1f.2
logical name: scsi0
logical name: scsi1
version: 02
width: 32 bits
clock: 66MHz
capabilities: ide bus_master emulated scsi-host
configuration: driver=ata_piix
resources: ioport:ec00-ec07 ioport:e800-e803 ioport:e400-e407
ioport:e000-e003 ioport:dc00-dc0f irq:185
*-disk:0
description: SCSI Disk
product: Maxtor 7H500F0
vendor: ATA
physical id: 0
bus info: scsi@0.0:0.0
logical name: /dev/sda
version: HA43
size: 465GB
configuration: ansiversion=5
*-disk:1
description: SCSI Disk
product: SAMSUNG HD501LJ
vendor: ATA
physical id: 1
bus info: scsi@1.0:0.0
logical name: /dev/sdb
version: CR10
size: 465GB
configuration: ansiversion=5
I do see that both disks are under "ide:1". Is that what you mean?
> This is not something from mdadm, anyway.
> Once the disk "dies" you are losing the disk bus, and that is "all she
> wrote".
So mdadm can't protect against disk failures on these machines? Whenever
a disk returns a write error, the machine will lock up?
--
Robert L Mathews
"In the beginning, the universe was created. This has made a lot of
people very angry and has been widely regarded as a bad move."
-- Douglas Adams
next prev parent reply other threads:[~2008-03-31 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 23:22 RAID 1 failure on single disk causes disk subsystem to lock up Robert L Mathews
2008-03-31 10:01 ` Justin Piszcz
2008-03-31 17:30 ` Robert L Mathews
2008-03-31 19:12 ` Justin Piszcz
[not found] ` <47F0281F.1070404@harddata.com>
2008-03-31 17:27 ` Robert L Mathews [this message]
2008-03-31 19:54 ` Peter Grandi
2008-04-01 19:33 ` Richard Scobie
2008-04-02 18:33 ` Robert L Mathews
2008-04-03 21:01 ` Peter Grandi
2008-04-04 19:11 ` Robert L Mathews
2008-04-02 17:43 ` Bill Davidsen
2008-04-02 18:42 ` Robert L Mathews
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=47F11F12.7010309@tigertech.com \
--to=lists@tigertech.com \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).