Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 1 results
    • https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Does_service_multipathd_reload_command_interrupt_any_previous_multipathd_working_connections
      It is safe to reload multipathd daemon while device-mapper-multipath paths are in use, as it does not impact any existing paths. Looking through the /etc/init.d/multipathd script in reload section, we...It is safe to reload multipathd daemon while device-mapper-multipath paths are in use, as it does not impact any existing paths. Looking through the /etc/init.d/multipathd script in reload section, we see the following code: reload() { 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.