public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jeff Garzik <jeff@garzik.org>,
	"Dr. J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: NFSv4 poops itself
Date: Fri, 27 Jul 2007 13:09:38 -0400	[thread overview]
Message-ID: <1185556178.6586.40.camel@localhost> (raw)
In-Reply-To: <1185543187.6586.10.camel@localhost>

On Fri, 2007-07-27 at 09:33 -0400, Trond Myklebust wrote:
> On Fri, 2007-07-27 at 08:53 -0400, Jeff Garzik wrote:
> > Background:
> > 
> > Server: x86-64 dual core Intel, kernel 2.6.23-rc1 (my home fileserver)
> > 	Exporting NFS/NFSv4 mounts.  Client count: 1  Uptime: 4 days
> > 
> > Client: x86-64 dual core Intel, kernel 2.6.23-rc1 (my main workstation)
> > 	NFS mount setup:
> > 	pretzel:/ on /g type nfs4 (rw,noatime,proto=tcp,addr=10.10.10.1)
> > 	Uptime: 4 days
> > 
> > 	Home directory mounted via NFSv4.
> > 
> > Problem:
> > 
> > My workstation has been happily talking to my file server for several 
> > days without incident.  An hour ago, my numeric keypad stopping working 
> > (unrelated problem... USB or X bug?).  The solution to the keypad 
> > problem is usually to log out of X and log back in, or worse case, reboot.
> > 
> > So, I log out, and log back in.  At first, a few shell windows open and 
> > successfully initialize themselves (read bash profile over NFS, etc.) 
> > Then, as more shell windows open, things start hanging.  I can easily 
> > switch to console and ssh to the fileserver, so it is clear this is an 
> > NFS hang.
> > 
> > No adverse messages at all on the client.
> > 
> > On the server, I see NFSv4 spamming dmesg with hundreds of thousands of 
> > messages:
> > 
> > Jul 27 08:20:53 pretzel kernel: NFSD: preprocess_seqid_op: old stateid!
> > Jul 27 08:21:24 pretzel last message repeated 167966 times
> > Jul 27 08:21:55 pretzel last message repeated 173628 times
> > Jul 27 08:21:55 pretzel kernel: NFSD: preprocess_seqid_op: old stateid!
> > Jul 27 08:22:26 pretzel last message repeated 171286 times
> > Jul 27 08:23:27 pretzel last message repeated 344461 times
> > Jul 27 08:23:30 pretzel last message repeated 18656 times

Jeff and Bruce, could you please try to reproduce the problem after
either applying patches 001 to 004 or just the single NFS_ALL patch
from 

   http://client.linux-nfs.org/Linux-2.6.x/2.6.23-rc1/

Cheers
  Trond

  reply	other threads:[~2007-07-27 17:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 12:53 NFSv4 poops itself Jeff Garzik
2007-07-27 13:33 ` Trond Myklebust
2007-07-27 17:09   ` Trond Myklebust [this message]
2007-07-27 17:16     ` Jeff Garzik
2007-07-27 17:29       ` Trond Myklebust
2007-08-03 19:13         ` J. Bruce Fields
2007-08-06 13:40           ` J. Bruce Fields
2007-08-06 18:40             ` Trond Myklebust
2007-07-27 18:29     ` Marc Dietrich
2007-07-27 13:36 ` Marc Dietrich
2007-07-27 13:40   ` Jeff Garzik
2007-07-27 14:45     ` Trond Myklebust
2007-07-27 14:58   ` Satyam Sharma
2007-07-27 17:58     ` Marc Dietrich
2007-07-27 18:39       ` Trond Myklebust

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=1185556178.6586.40.camel@localhost \
    --to=trond.myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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