All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@poochiereds.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS List <nfs@lists.sourceforge.net>, nfsv4@linux-nfs.org
Subject: Re: [NFS] Missing handling for NFS4ERR_OLD_STATEID	in	nfs4_handle_exception?
Date: Thu, 12 Apr 2007 13:49:16 -0400	[thread overview]
Message-ID: <461E711C.9040202@poochiereds.net> (raw)
In-Reply-To: <1176399064.6664.22.camel@heimdal.trondhjem.org>

Trond Myklebust wrote:
> On Thu, 2007-04-12 at 07:59 -0400, Jeff Layton wrote:
> 
>> This sounds sort of like addressing the symptom and not the real 
>> problem, however. The real question ought to be why you're getting 
>> OLD_STATEID errors back from the server here. There can be legit 
>> reasons, but these errors ought to be fairly rare. I generally only have 
>> seen them when processes are signalled while RPC requests are in flight.
> 
> OLD_STATEID usually occurs if an OPEN or an OPEN_DOWNGRADE gets sent
> that changes the current stateid while a READ or WRITE to the same file
> is in flight.
> 
> It is generally a rare event, and so it tends to be much easier to deal
> with by simply resending the READ/WRITEs with the updated stateid rather
> than adding an expensive locking scheme for excluding READ/WRITE while
> the OPEN/OPEN_DOWNGRADE is in progress.
> 
> Cheers,
>   Trond
> 

Ahh that makes sense. I must have misunderstood the circumstances where 
I was seeing it. Thanks for clarifying.

-- Jeff

  reply	other threads:[~2007-04-12 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 16:09 Missing handling for NFS4ERR_OLD_STATEID in nfs4_handle_exception? Frank Filz
2007-04-12 11:59 ` Jeff Layton
2007-04-12 17:11   ` Frank Filz
2007-04-12 17:51     ` Jeff Layton
2007-04-12 17:31   ` [NFS] " Trond Myklebust
2007-04-12 17:49     ` Jeff Layton [this message]
2007-04-12 18:07 ` Trond Myklebust
2007-04-18 13:57   ` Jeff Layton
2007-04-23 17:14     ` Frank Filz
2007-04-24 12:28       ` Jeff Layton

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=461E711C.9040202@poochiereds.net \
    --to=jlayton@poochiereds.net \
    --cc=nfs@lists.sourceforge.net \
    --cc=nfsv4@linux-nfs.org \
    --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 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.