[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47A38F33.9050505@redhat.com>
Date: Fri, 01 Feb 2008 16:29:23 -0500
From: Peter Staubach <staubach@...hat.com>
To: Trond Myklebust <trond.myklebust@....uio.no>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-nfs@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 3/3] enhanced NFS ESTALE error handling (v2)
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists