All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: Fw: [Bug 208807] New: Problem with NFS kernel server code
Date: Tue, 4 Aug 2020 17:21:28 -0400	[thread overview]
Message-ID: <20200804212128.GC25981@fieldses.org> (raw)
In-Reply-To: <20200804140744.35ce4bdd@hermes.lan>

Commented, but I guess it should really be reassigned to nfsd, I'm not
sure how.

--b.

On Tue, Aug 04, 2020 at 02:07:44PM -0700, Stephen Hemminger wrote:
> 
> 
> Begin forwarded message:
> 
> Date: Tue, 04 Aug 2020 11:33:23 +0000
> From: bugzilla-daemon@bugzilla.kernel.org
> To: stephen@networkplumber.org
> Subject: [Bug 208807] New: Problem with NFS kernel server code
> 
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=208807
> 
>             Bug ID: 208807
>            Summary: Problem with NFS kernel server code
>            Product: Networking
>            Version: 2.5
>     Kernel Version: 5.8.0
>           Hardware: All
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>           Assignee: stephen@networkplumber.org
>           Reporter: nanook@eskimo.com
>         Regression: No
> 
> Created attachment 290759
>   --> https://bugzilla.kernel.org/attachment.cgi?id=290759&action=edit  
> Output of dmesg while machine was dying
> 
> After about an hour and a half of operating on 5.8.0, one of our NFS servers
> began to slow and basically ground to a halt.  Looks like a spinlock issue in
> the NFS kernel server code.  I'll attach the output of dmesg while the machine
> was dying in a file called "spinlock".  A shame because while it was running,
> the performance of 5.8 was astounding.  Only the NFS servers seem to get ill,
> the
> client machines seem to run fine on 5.8 so far at least.
> 
> -- 
> You are receiving this mail because:
> You are the assignee for the bug.

      reply	other threads:[~2020-08-04 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 21:07 Fw: [Bug 208807] New: Problem with NFS kernel server code Stephen Hemminger
2020-08-04 21:21 ` J. Bruce Fields [this message]

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=20200804212128.GC25981@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.