From: "Gordon Mohr (@ Bitzi)" <gojomo@bitzi.com>
To: linux-raid@vger.kernel.org
Subject: Questions: understanding fail/remove steps from RAID1
Date: Sat, 12 Feb 2005 14:11:07 -0800 [thread overview]
Message-ID: <420E7EFB.4000303@bitzi.com> (raw)
I've been experiencing as-yet-undiagnosed kernel panics on a server
with two RAID1 arrays. (x86_64; 2.6.10 FC3 kernel; Promise SATA with
Seagate drives.)
After a recent panic and reboot, the two RAID1 arrays dropped their
member partitions from a certain drive (sdb).
Based on previous experience with simulated failures, I had expected
the devices to still be listed by name as part of the array, but as
failed/faulty. Instead, they were not listed in either /proc/mdstat
or 'mdadm --detail' output.
Were my expectations wrong -- is this by design?
Looking over /var/log/messages, there's no clear indication of a
specific time or reason the sdb partitions were dropped from the array.
Are raid array events logged somewhere else?
Thanks for any insights,
- Gordon
reply other threads:[~2005-02-12 22:11 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=420E7EFB.4000303@bitzi.com \
--to=gojomo@bitzi.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).