Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
NetApp Knowledge Base

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

Views:
2,128
Visibility:
Public
Votes:
0
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.