Inoperative array shown as "active"
I'm in the process of writing a program to monitor various aspects of my NAS. As part of this effort, I've been simulating RAID disk failures in a VM, and I noticed something that seems very odd.
Namely, when a sufficient number of disks has been removed from a RAID-5 or RAID-6 array to make it inoperable, the array is still shown as "active" in /proc/mdstat and "clean" in the sysfs array_state file. For example:
md0 : active raid5 sde[3](F) sdd[2] sdc[1](F) sdb[0]
6286848 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/2] [U_U_]
(mdadm does show the state as "clean, FAILED".)
Is this the expected behavior?
AFAICT, this means that there is no single item in either /proc/mdstat or sysfs that indicates that an array such as the example above has failed. My program will have to parse the RAID level, calculated the number of failed members (if any), and determine whether that RAID level can survive that number of failures. Is this correct?
Anything I'm missing?
Thanks!
Signature · 4 lines
======================================================================== Ian Pilcher [email protected] Sometimes there's nothing left to do but crash and burn...or die trying. ========================================================================
Quoted 9 lines · On Sat, 14 Sep 2013 00:39:20 -0500 Ian Pilcher <[email protected]> wrote:
I'm in the process of writing a program to monitor various aspects of my NAS. As part of this effort, I've been simulating RAID disk failures in a VM, and I noticed something that seems very odd.
Namely, when a sufficient number of disks has been removed from a RAID-5 or RAID-6 array to make it inoperable, the array is still shown as "active" in
/proc/mdstatand "clean" in the sysfsarray_statefile. For example:
Quoted 6 lines
md0 : active raid5 sde[3](F) sdd[2] sdc[1](F) sdb[0]
6286848 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/2] [U_U_](mdadm does show the state as "clean, FAILED".)
Is this the expected behavior?
Yes.
Quoted 6 lines
AFAICT, this means that there is no single item in either
/proc/mdstator sysfs that indicates that an array such as the example above has failed. My program will have to parse the RAID level, calculated the number of failed members (if any), and determine whether that RAID level can survive that number of failures. Is this correct?
Yes.
Quoted 2 lines
Anything I'm missing?
mdadm already does this for you. "mdadm --detail /dev/md0".
NeilBrown
Quoted 3 lines
Thanks!
Quoted 7 lines · NeilBrown
Quoted 5 lines · On Sat, 14 Sep 2013 00:39:20 -0500 Ian Pilcher <[email protected]> wrote:
AFAICT, this means that there is no single item in either
/proc/mdstator sysfs that indicates that an array such as the example above has failed. My program will have to parse the RAID level, calculated the number of failed members (if any), and determine whether that RAID level can survive that number of failures. Is this correct?
Quoted 7 lines
Yes.
Quoted 2 lines
Anything I'm missing?
mdadm already does this for you. "mdadm --detail
/dev/md0".
Yeah, I haven't yet ruled out calling out to mdadm. I'm already doing that with hddtemp and smartctl. It just seems a bit inefficient to do so when all of the information is sitting right there in /proc/mdstat.
A quick test reveals that running "mdadm --detail /dev/md?*" takes around 2 seconds on the NAS and produces about 20KB of output. (I have 20 RAID devices -- hooray GPT! -- and an Atom processor.) Hmmm.
Thanks for the very quick response!
Signature · 4 lines
======================================================================== Ian Pilcher [email protected] Sometimes there's nothing left to do but crash and burn...or die trying. ========================================================================