:)
> @protonmail.com> @protonmail.com>
obsd's mount_nfs is a trap, because it executes a "hard" mount by default.
This is not a wise default, if you consider the consequences of a hard nfs
mount gone bad.
A wiser default would be a soft interruptible mount.
This reminds me of the "format" command in DOS 2.11: as people complained ha
More info...
obsd mounted the nfs folder on /mnt/nas, there is an unknown problem on the io
with the nas, and "ls /mnt/nas" locks the console instead of terminating with
information on the problem.
Before mounting /mnt/nas, obsd had a hot-swap disk mounted on /mnt/backup,
alive and well. After
NFS case study.
- obsd server mounts LAN resource via NFS
- the NFS server is a NAS running Alt-F firmware version 1.0 with working ssh
but without sudo;
- the NFS link does not respond
- all obsd related processes hang into D state, including command like ls, df,
and reboot.
- kill -9 does not
4 matches
Mail list logo
