public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Joschi Brauchle <joschi.brauchle@tum.de>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Syslog flooded: "NFSD: preprocess_seqid_op: magic stateid!"
Date: Wed, 16 Jun 2010 22:32:57 -0400	[thread overview]
Message-ID: <20100617023257.GB20645@fieldses.org> (raw)
In-Reply-To: <501A322854D4C944BCAF0528CFC7B65E3B30E7F5EE-7sgYbYbIMHsZ3TY+6YjGZ+/kjxG1y2if@public.gmane.org>

On Wed, Jun 16, 2010 at 10:20:15AM +0200, Joschi Brauchle wrote:
> Second problem:
> We recently downgraded from a patched nfs-utils 1.0.9 (patched to acc=
ept the =E2=80=9C-h=E2=80=9D option for different hostname in Kerberos =
service creds in a high availability environment) to the original Novel=
l RPM providing nfs-utils 1.0.7 (now using the undocumented =E2=80=9C-c=
=E2=80=9D switch to read the accepted creds from keytab file). (Note: t=
he first problem has already occurred before this downgrade)
>=20
> Since this change, we are experiencing massive lags (1-10 sec freezes=
, irregularly, but a couple times an hour) on our client machines, whic=
h are mounting their homes via NFSv4. There seem to be no related messa=
ges or warnings on the server nor the clients.
>=20
> We come to the conclusion that 1.0.9 was the more stable version. The=
 resulting question is: Which nfs-utils version would be best suited fo=
r SLES10SP3 (see kernel version above). Can we go straight to the lates=
t 1.2.2 available or should we stick with 1.0.xx version?

No idea.  We'd have to figure out the cause of the lags.

--b.

      parent reply	other threads:[~2010-06-17  2:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  8:20 Syslog flooded: "NFSD: preprocess_seqid_op: magic stateid!" Joschi Brauchle
     [not found] ` <501A322854D4C944BCAF0528CFC7B65E3B30E7F5EE-7sgYbYbIMHsZ3TY+6YjGZ+/kjxG1y2if@public.gmane.org>
2010-06-17  2:31   ` J. Bruce Fields
2010-06-17  2:32   ` 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=20100617023257.GB20645@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=joschi.brauchle@tum.de \
    --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