Skip to main content

Coming soon...New Support-Specific categorization of Knowledge Articles in the NetApp Knowledge Base site to improve navigation, searchability and your self-service journey.

NetApp Knowledge Base

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

Views:
4,281
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.

 

Scan to view the article on your device