monitoring multipath arrays plus inconsistent /proc/mdstat?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

mdadm --monitor or mdadm --follow does not report anything if a link to my multipath array fails, which makes sense at times. (?)

On rhel 2.1 at least, sometimes I have seen that /proc/mdstat is not consistent as in this case, it has marked /dev/sdi as failed, where as mdadm -D on md3 has reported both links to be active, and in fact is using the "failed link" in mdstat as the active path..!!

------------------from /proc/mdstat---------------------------------------
md3 : active multipath sdd[1] sdi[0](F)

----------------from mdadm o/p--------------------------
[root@tlr root]# mdadm -D /dev/md3
/dev/md3:
<snip>
<snip>
   Number   Major   Minor   RaidDevice State
      0       8      128        0      active sync   /dev/sdi

      1       8       48        1      spare   /dev/sdd

----------------------------------------------------------------------------

Whom to trust here? How do we monitor multipath arrays effectively?

--Matt
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux