I have faced a problem recently with a NFS mapping. An I/O process (
cp) got in uninterruptible sleep state and I ended up having to reboot the machine to fix the problem. Rebooting was bad so I don't want this to happen again.
It was mounted as follows:
mount //path/to/network/drive /path/to/folder -o domain=DOMAIN_HERE,username=USERNAME_HERE
It was a CIFS mount because the
//path/to/network/drive is a windows filesystem (but I assume the command above figured this out automatically, since I didn't specify CIFS explicitly).
Upon investigating I found out that it was a "hard-mount" and that was a part of the problem. I found that a "soft-mount" could have helped, and also the
intr option could have helped too.
So now I want to mount it again, but instead of simply calling the above command, I was thinking of calling it as follows:
mount //path/to/network/drive /path/to/folder -o soft,intr,domain=DOMAIN_HERE,username=USERNAME_HERE
Does this work? Are
intr compatible? I don't understand deeply what they do exactly but I've seen that they should help prevent the same issue from happening again because nothing would ever reach the uninterruptible sleep state with them. Also, since apparently option order matters, is the ordering above ok?