On Tue, 2018-11-13 at 08:17 +0800, Ed Greshko wrote:
On 11/13/18 7:33 AM, Patrick O'Callaghan wrote:
> Following up on this last, I wondered if the problem could be NFS-
> related. I have an NFS volume only used for backup and mounted from my
> NAS, so tried using 'fuser' to pin down what could be using it, but
> 'fuser' itself just sat there with no results. Curiouser and curiouser.
>
> I masked out the NFS mount from /etc/fstab and rebooted. I've now been
> running for 48 hours with no freezes or hangs, so I'm tentatively
> calling this an NFS bug. I might try re-enabling it using automount
> just for kicks.
>
> Not sure what else I can provide to BZ to make it debuggable, as
> plasmashell seems to be the only thing that triggers it.
I've got 4 NFS mounts on one system and 1 NFS mount on another. In the case of the
1
mount it is actually on a system using an IPv6 tunnel and the mount is done on IPv6.
This
means the network path is from Taiwan, through the US, and back to Taiwan. (This is
just
for testing).
Neither of my systems are having any freezes and both are up 24/7.
I use...
nfs4 rw,soft,fg,x-systemd.automount
in my fstab
Thanks Ed. My entry is:
nfs user,rw,async,comment=systemd.mount 0 0
I'll try using your parameters and see what happens. The NAS is an old
device, probably with NFS3 (or even 2).
poc