LKML Archive on
help / color / mirror / Atom feed
From: Peter Staubach <>
To: Trond Myklebust <>
Cc: Linux Kernel Mailing List <>,,
	Andrew Morton <>,
	linux-fsdevel <>
Subject: Re: [PATCH 3/3] enhanced NFS ESTALE error handling (v2)
Date: Fri, 01 Feb 2008 16:29:23 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Trond Myklebust wrote:
> On Fri, 2008-02-01 at 15:58 -0500, Peter Staubach wrote:
>> Hi.
>> The patch enhanced the ESTALE error handling for NFS mounted
>> file systems.  It expands the number of places that the NFS
>> client checks for ESTALE returns from the server.
>> It also enhances the ESTALE handling for directories by
>> occasionally retrying revalidation to check to see whether the
>> directory becomes valid again.  This sounds odd, but can occur
>> when a systems administrator, accidently or unknowingly,
>> unexports a file system which is in use.  All active
>> non-directory files become permanently inaccessible, but
>> directories can be become accessible again after the
>> administrator re-exports the file system.  This is a situation
>> that users have been complaining about for years and this
>> support can help to alleviate their situations.
> As far as I can see, this patch can be applied separately from the VFS
> fixes. If so, would it make sense for me to take charge of this patch in
> the NFS tree, while Andrew queues up the other two VFS changes in -mm?

Yes, I think that this would make good sense.



  reply	other threads:[~2008-02-01 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:36 [PATCH 3/3] enhanced ESTALE error handling Peter Staubach
2008-02-01 20:58 ` [PATCH 3/3] enhanced NFS ESTALE error handling (v2) Peter Staubach
2008-02-01 21:06   ` Trond Myklebust
2008-02-01 21:29     ` Peter Staubach [this message]
2008-03-10 20:23   ` [PATCH 3/3] enhanced NFS ESTALE error handling (v3) Peter Staubach

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: [PATCH 3/3] enhanced NFS ESTALE error handling (v2)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).