From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Linux-Raid <linux-raid@vger.kernel.org>
Subject: force a raid restart?
Date: Mon, 27 Jan 2003 09:44:57 -0500 [thread overview]
Message-ID: <20030127144457.GA8989@rdlg.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
Scenario:
System has 2 3ware IDE raid controllers. Controller 1 has 8 disks
installed built out as 2 software 4disk RAID5 arrays, built using
"raidtools" mkraid.
Disk 0 (first array) physically failed array running in degraded mode.
Disk 5 (second array) failed 2 days later but at this time generated
enough IO to hang up the controller. This appears to have caused the
raid subsystem to mark disk1 (first array) bad also. It's passed a
number of disk tests and seems ok.
As a result md0 is dead because of disk0 and disk1. Is there a way to
force it to restart md0 since when it read disk1 dead it just stopped
the array? The data should all be in tact, just degraded since disk0 is
physcially dead and off for RMA? I've installed mdadm and am reading
the docs but I need this back quickly if it's possible.
Also, we use devfs. I've seen in the /etc/raidtab most of the time it's
built referencing /dev/hdX or /dev/sdX. Since these move around alot is
there any reason other than length why we shouldn't use the
/dev/scsi/host...* devices?
Robert
:wq!
---------------------------------------------------------------------------
Robert L. Harris | PGP Key ID: FC96D405
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
FYI:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-01-27 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030127144457.GA8989@rdlg.net \
--to=robert.l.harris@rdlg.net \
--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).