My thought was to combine patch 2 and 3 unless it was felt that disallowing
more than one Multipath pool to defined at one time (patch 3) was unnecessary
For patch 1, I did some searching and came across the following to describe
why /dev/mpath is no longer valid:
http://comments.gmane.org/gmane.linux.kernel.device-mapper.devel/13864
I kept /dev/mpath as a valid option only just in case there's some strange
back-compat issue or some platform where /dev/mpath is preferred/used
instead of /dev/mapper.
John Ferlan (3):
mpath: Update path in CheckPool function
docs: Clarify the Multipath target path value usage
mpath: Don't allow more than one mpath pool at a time
docs/formatstorage.html.in | 2 ++
docs/storage.html.in | 3 ++-
src/conf/storage_conf.c | 3 +++
src/storage/storage_backend_mpath.c | 3 ++-
4 files changed, 9 insertions(+), 2 deletions(-)
--
2.1.0