4 ms·

I've encountered issue when NFS mount can block regular system reboot when the network connection is broken.

• nubinetwork 3y ago
  Interesting. I would have figured systemd would have coded around that. (Not that I've tried)
  • antiloper 3y ago
    A process that's stuck on an NFS operation is unkillable, even by a SIGKILL from the root user. So any shutdown/reboot procedure that has a "kill all processes" step will be unable to complete (unless it has a timeout). It sounds like systemctl --force --force reboot will just invoke the `reboot` syscall directly and thus avoid this issue.
    • znpy 3y ago
      Yeah, that happens when a process is in D state (uninterruptible sleep). This happens for example if the process is waiting for io from a block device that has gone forever, like an nfs mount with a broken connection, but i also remember this happening in a company where somebody had the unfortunate idea of “retrofitting” (I’m using kind words here…) zfs to run on some rhel6 hosts, and it would hang very often (of course… but hey, we get snapshots without paying for a netapp).