| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This reverts commit 74e65cbf111a4f17fa393192519910de53d6c7ac.
|
|
|
|
| |
This reverts commit a24e722ebcb06c88f88605190caebdcf83236690.
|
| |
|
|
|
|
|
| |
If we don't have a multipath.conf when we scan, we get a default blacklist
of everything, which isn't helpful. So write one.
|
| |
|
| |
|
|
|
|
|
| |
Format strings need to match the things being formatted, as Hans
correctly pointed out.
|
|
|
|
|
| |
Use device-mapper-multipath's "multipath" tool to find and set up
multipath devices.
|
|
|
|
|
|
|
|
| |
Revamp this since multipath is now writing our rules for us.
Use device.serial/device.vendor/device.model where appropriate, and
don't give the device a braindead mode. Also change /when/ we write the
files out.
|
|
|
|
|
| |
We need to find out about multipath topology from /sbin/multipath, which
unfortunately needs some parsing - it's fairly easy, though.
|
|
|
|
|
|
|
|
| |
The return type has also changed. It now returns a tuple of a list of regular
devices, a list of multipath sets, and a list of partition devices. This is
necessary so the filtering UI can use the same knowledge that was in the
DeviceTree object to know which devices are part of a multipath set and which
are just standalone disks.
|
|
|
|
|
|
| |
Use "device" entries in the config file rather than specifying
configuration parameters in the "multipath" section of the config file.
This gets us more reasonable configuration.
|
|
This writes a multipathd.conf that whitelists the devices we're using in
our multipath devices. It's a fairly basic configuration, and it doesn't
handle ALUA yet.
|