All of lore.kernel.org
 help / color / mirror / Atom feed
* Questions: understanding fail/remove steps from RAID1
@ 2005-02-12 22:11 Gordon Mohr (@ Bitzi)
  0 siblings, 0 replies; only message in thread
From: Gordon Mohr (@ Bitzi) @ 2005-02-12 22:11 UTC (permalink / raw)
  To: linux-raid

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-02-12 22:11 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-12 22:11 Questions: understanding fail/remove steps from RAID1 Gordon Mohr (@ Bitzi)

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.