On Wed, 2018-11-14 at 18:00 +0800, Ed Greshko wrote:
On 11/14/18 5:51 PM, Patrick O'Callaghan wrote:
> On Wed, 2018-11-14 at 06:21 +0800, Ed Greshko wrote:
> > On 11/14/18 6:10 AM, Patrick O'Callaghan wrote:
> > > On Tue, 2018-11-13 at 14:25 -0600, Rex Dieter wrote:
> > > > Patrick O'Callaghan wrote:
> > > >
> > > > > On Tue, 2018-11-13 at 17:00 +0000, Patrick O'Callaghan
> > > > > > > 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).
> > > > > > Nope, just froze again. This is with your options but I
> > > > > > that matters.
> > > > > Or maybe it does. After freezing for an appreciable time
> > > > > has now spontaneously unfrozen itself. I'll keep an eye on
it and see
> > > > > if it happens again.
> > > > I suspect it may be a one or both of these that made a difference:
> > > > automount
> > > >
> > > > (I'd bet on soft... ie, the mount becomes unresponsive, but now
> > > > can continue despite that)
> > > Perhaps. It just did it again. This time the pause was around 10-12
> > > minutes. Note that the only thing that stops (apparently) is
> > > plasmashell. The rest of the system continues working normally and I
> > > can switch desktops using Ctrl-Fn with no problem.
> > >
> > Is your mount point within your home directory space?
> > If so, can you mount it elsewhere to see if the problem continues?
> No, it's under a root directory.
I see. How about a symlink from your home directory to it?
The reason I ask is that I had an issue a while back, can't recall the full details,
I'd have a pause of several seconds when there was a symlink to a mount point.
like it may have been some sort of "look ahead" issue. I decided the symlink
buying me anything so I removed it and really didn't investigate.
No. (I double-checked to be sure). And we're not talking about several
seconds but many minutes or even hours.
Does your NAS have any logs which may indicate a connection issue at
No. When this has happened I've been able to log into the NAS with no
problem. It's logs show nothing wrong.
It seems to be completely random. The panel freezes when I'm not even
using it and I only notice when I try and click on something or notice
the clock widget is showing the wrong time. Debugging doesn't work
because gdb can't attach to a process in 'D' state (IIRC because
ptrace() requires the kernel-level process to run code and it's
blocked). Equally mysterious is how it suddenly unblocks itself.