summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorHannes Reinecke <hare@suse.de>2009-06-22 10:12:11 +0100
committerAlasdair G Kergon <agk@redhat.com>2009-06-22 10:12:11 +0100
commita0cf7ea9549ec60988369f90e5c0f855f08abac9 (patch)
tree9a073e2360afebe6485ac3a78c796627fc9e80b2 /Documentation
parent4d89b7b4e4726893453d0fb4ddbb5b3e16353994 (diff)
downloadtalos-obmc-linux-a0cf7ea9549ec60988369f90e5c0f855f08abac9.tar.gz
talos-obmc-linux-a0cf7ea9549ec60988369f90e5c0f855f08abac9.zip
dm mpath: change attached scsi_dh
When specifying a different hardware handler via multipath features we should be able to override the built-in defaults. The problem here is the hardware table from scsi_dh is compiled in and cannot be changed from userland. The multipath.conf OTOH is purely user-defined and, what's more, the user might have a valid reason for modifying it. (EG EMC Clariion can well be run in PNR mode even though ALUA is active, or the user might want to try ALUA on any as-of-yet unknown devices) So _not_ allowing multipath to override the device handler setting will just add to the confusion and makes error tracking even more difficult. Signed-off-by: Hannes Reinecke <hare@suse.de> Signed-off-by: Alasdair G Kergon <agk@redhat.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud