From: Peter Staubach <staubach-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Trond Myklebust
<trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org>
Cc: Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 3/3] enhanced NFS ESTALE error handling (v2)
Date: Fri, 01 Feb 2008 16:29:23 -0500 [thread overview]
Message-ID: <47A38F33.9050505@redhat.com> (raw)
In-Reply-To: <1201900017.11291.43.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
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.
Thanx...
ps
-
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent 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
[not found] ` <4790C76F.2050105-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-02-01 20:58 ` [PATCH 3/3] enhanced NFS ESTALE error handling (v2) Peter Staubach
2008-02-01 21:06 ` Trond Myklebust
[not found] ` <1201900017.11291.43.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-01 21:29 ` Peter Staubach [this message]
[not found] ` <47A387D9.1070206-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
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:
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=47A38F33.9050505@redhat.com \
--to=staubach-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).