Re: NFS leading to D-state processes

2017-11-06 Thread Rupert Gallagher
:)

> @protonmail.com> @protonmail.com>

Re: NFS leading to D-state processes

2017-11-06 Thread Rupert Gallagher
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 hard, 
the command was modified to ask: "are you sure?"

Sent from ProtonMail Mobile

On Sun, Nov 5, 2017 at 15:29, Rupert Gallagher  wrote:

> 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 mounting /mnt/nas, "ls /mnt/backup" locks the console 
> as well.
>
> ---The evolution of ICT: hardware, software, crapware, abandonware.
>
> Sent from ProtonMail Mobile
>
> On Sat, Nov 4, 2017 at 13:40, Rupert Gallagher  wrote:
>
>> 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 work: 
>> the kernel locked them - umount -f does not work - reboot kills the server: 
>> tried locally, it hangs, forever - obsd hard reset not possible: it sits 
>> overseas, without manpower I need fresh ideas to unlock the kernel ... 
>> locked processes and kill the nfs link. Sent from ProtonMail Mobile

Re: NFS leading to D-state processes

2017-11-05 Thread Rupert Gallagher
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 mounting /mnt/nas, "ls /mnt/backup" locks the console as 
well.

---The evolution of ICT: hardware, software, crapware, abandonware.

Sent from ProtonMail Mobile

On Sat, Nov 4, 2017 at 13:40, Rupert Gallagher  wrote:

> 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 work: the 
> kernel locked them - umount -f does not work - reboot kills the server: tried 
> locally, it hangs, forever - obsd hard reset not possible: it sits overseas, 
> without manpower I need fresh ideas to unlock the kernel ... locked processes 
> and kill the nfs link. Sent from ProtonMail Mobile

NFS leading to D-state processes

2017-11-04 Thread Rupert Gallagher
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 work: the kernel locked them
-  umount -f does not work
- reboot kills the server: tried locally, it hangs, forever
- obsd hard reset not possible: it sits overseas, without manpower

I need fresh ideas to unlock the kernel ... locked processes and kill the nfs 
link.

Sent from ProtonMail Mobile