> And if, for some reason, multipathd wasn't monitoring a path it should > be, the best thing to do is to reconfigure multipathd. Code that > watched multipath.conf and automatically reconfigured multipathd when it > changed would be a nice addition though. I'd suggest an explicit warning of unmonitored paths in syslog rather than an automagic reconfiguration. A simple typo in multipath.conf could cause the loss of a whole lot of data if automatic reconfigs are happening. - Jerry -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel