From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Stuart Anderson <anderson@ligo.caltech.edu>,
MalteSch@gmx.de, nfs@lists.sourceforge.net
Subject: Re: Kernel NFS nfs_update_inode Oops in 2.6.20.11
Date: Wed, 27 Jun 2007 22:22:35 -0400 [thread overview]
Message-ID: <20070628022235.GC20605@fieldses.org> (raw)
In-Reply-To: <1182986558.5311.70.camel@heimdal.trondhjem.org>
On Wed, Jun 27, 2007 at 07:22:38PM -0400, Trond Myklebust wrote:
> On Wed, 2007-06-27 at 16:04 -0700, Stuart Anderson wrote:
> > This has patch has now been stable for 5 days on two different machines.
> >
> > Any thoughts about the "bad sequence-id error"?
>
> I seem to remember that a couple of sources of state corruption were
> found in the server in and around the 2.6.20 series. Do I remember
> correctly, Bruce?
I don't remember any (and don't see any relevant patches in a quick skim
of 'git log fs/nfsd').
Which isn't to say we couldn't have some problem there....
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-06-28 2:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 15:33 Kernel NFS nfs_update_inode Oops in 2.6.20.11 Stuart Anderson
2007-06-23 16:11 ` Trond Myklebust
2007-06-23 16:52 ` Stuart Anderson
2007-06-23 21:51 ` Stuart Anderson
2007-06-27 23:04 ` Stuart Anderson
2007-06-27 23:22 ` Trond Myklebust
2007-06-27 23:26 ` Stuart Anderson
2007-06-27 23:34 ` Trond Myklebust
2007-06-28 0:56 ` Chuck Lever
2007-06-28 1:26 ` Trond Myklebust
2007-06-28 2:22 ` J. Bruce Fields [this message]
2007-06-28 17:08 ` Malte Schröder
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=20070628022235.GC20605@fieldses.org \
--to=bfields@fieldses.org \
--cc=MalteSch@gmx.de \
--cc=anderson@ligo.caltech.edu \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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