linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@gmail.com>
To: Alan Post <adp@prgmr.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: User process NFS write hang followed by automount hang requiring reboot
Date: Fri, 24 May 2019 15:19:22 -0400	[thread overview]
Message-ID: <CAABAsM7DPHJyrfsOuse-wv4Vxwbd5BZ4DXQnAOiV7jVJE6sp2Q@mail.gmail.com> (raw)
In-Reply-To: <20190524173155.GQ4158@turtle.email>

On Fri, 24 May 2019 at 13:32, Alan Post <adp@prgmr.com> wrote:
>
> On Tue, May 21, 2019 at 03:46:03PM +0000, Trond Myklebust wrote:
> > Have you tried upgrading to 4.19.44? There is a fix that went in not
> > too long ago that deals with a request leak that can cause stack traces
> > like the above that wait forever.
> >
>
> Following up on this.  I have set aside a rack of machines and put
> Linux 4.19.44 on them.  They ran jobs overnight and will do the
> same over the long weekend (Memorial day in the US).  Given the
> error rate (both over time and over submitted jobs) we see across
> the cluster this well be enough time to draw a conclusion as to
> whether 4.19.44 exhibits this hang.
>
> Other than stack traces, what kind of information could I collect
> that would be helpful for debugging or describing more precisely
> what is happening to these hosts?  I'd like to exit from the condition
> of trying different kernels (as you no doubt saw in my initial message
> I've done a lot of it) and enter the condition of debugging or
> reproducing the problem.
>
> I'll report back early next week and appreciate your feedback,
>

Perhaps the output from 'cat /sys/kernel/debug/rpc_clnt/*/tasks'?

Thanks
  Trond

  reply	other threads:[~2019-05-24 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 22:33 User process NFS write hang followed by automount hang requiring reboot Alan Post
2019-05-21 15:46 ` Trond Myklebust
2019-05-21 19:22   ` Alan Post
2019-05-30 18:39     ` J. Bruce Fields
2019-05-31  0:22       ` Alan Post
2019-05-24 17:31   ` Alan Post
2019-05-24 19:19     ` Trond Myklebust [this message]
2019-05-30  0:41     ` Alan Post
2019-05-30  1:09       ` Trond Myklebust
2019-06-04 17:44       ` Alan Post

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAABAsM7DPHJyrfsOuse-wv4Vxwbd5BZ4DXQnAOiV7jVJE6sp2Q@mail.gmail.com \
    --to=trondmy@gmail.com \
    --cc=adp@prgmr.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).