Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.

NetApp KCS Award

NetApp Knowledge Base

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

Views:
2,874
Visibility:
Public
Votes:
1
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