Skip to contentSkip to conversation

multipath md devices

DISCUSSION Doug Griswold 1 participant 1 message Sep 22, 2004 MD RAID

lore
Share & tools
lore
#0 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line

Doug Ledford <[email protected]> 09/22/04 5:35 PM >>>

Quoted 4 lines · Anu Matthew

Hi,

We have multipath devices created on SAN Luns. Say md0 is created on /dev/sdj and /dev/sde, the latter being the alternate path for

/dev/sdj.

Quoted 5 lines

I've noticed the following:

1) Without much IO to the md device, and I pull out the cable to say /dev/sdj, the /proc/mdstat still shows both devices. /proc/mdstat

won't

Quoted 6 lines

get updated unless I start some considerable IO to the md device. Even

mdadm scan/query o/p shows both the paths, which is not true. As we start IO, /proc/mdstat reflects that one of the devices, /dev/sdj in this case, has failed. Thereafter mdadm outputs would be correct too.

Quoted 6 lines

The entries (link down) in syslog and dmesg are almost instantaneous when the cable is pulled out. This makes it very difficult to monitor multipath devices, as we cannot rely on /proc/mdstat to read.

/proc/mdstat will be correct once the first physical read/write on the yanked path fails.

Is this true even if the lightpath is not dead?

Quoted 6 lines

2) Another situation: Device md0 is active, with healthy multipaths /dev/sdj and /dev/sde, under reasonable IO activity. If the cable to /dev/sdj is yanked out, md0 remains still active, thanks to the alternate path, sde. However, it fails to go back and re-construct the

spare path allocation even after the fibre link is restored. Here, if

I

Quoted 4 lines

pull the cable out for sde even after 30 minutes, the machine ends up failing to write to /dev/md0 as it does not care whether /dev/sdj is back online, unless I failed, removed and add /dev/sdj manually from the mdadm command line. If something is hard mounted on /dev/md0, it

may

Quoted 8 lines

end up in a system crash.

To conclude, if one path goes off, and comes back after a while, and then the second path goes off, md0 cannot be read, unless someone manually did fail, remove and add the first device which came back online, before the second path goes off.

Yeah, IBM wrote a little app to help with that. We stuffed it into

the

Quoted 2 lines

mdadm package we ship since that seemed the most appropriate place for it. It's called mdmpd and that's it's job basically. Very simple

app,

Quoted 1 line

but doesn't run on upstream kernels at the moment (it wants the md

event

Quoted 9 lines

interface which hasn't yet been submitted upstream by Neil).

Any help towards this will be much appreciated.

Thanks,

--AM.
-
To unsubscribe from this list: send the line "unsubscribe linux-raid"

in

Quoted 2 lines

the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 10 lines
  Doug Ledford <[email protected]>     919-754-3700 x44233
         Red Hat, Inc.
         1801 Varsity Dr.
         Raleigh, NC 27606


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