Skip to main content
NetApp Knowledge Base

Does 'service multipathd reload' command interrupt any previous multipathd working connections ?

Views:
4,545
Visibility:
Public
Votes:
2
Category:
fas-systems
Specialty:
san
Last Updated:

 

Applies to

  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 5
  • Device-Mapper-Multipath

Answer

It is safe to reload multipathd daemon while device-mapper-multipath paths are in use, as it does not impact any existing paths.

Additional Information

Looking through the /etc/init.d/multipathd script in reload section, we see the following code:

reload() {

echo -n "Reloading $prog: "

trap "" SIGHUP

killproc $DAEMON -HUP

RETVAL=$?

echo

}

The reload process sends a HUP signal to the multipathd daemon, which causes it to re-read the configuration file.

Device-mapper-multipath functions without the multipathd daemon running, however without multipathd, path failures will not be detected or handled.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Scan to view the article on your device