From: Peter Staubach Subject: Re: [PATCH 3/3] enhanced NFS ESTALE error handling (v2) Date: Fri, 01 Feb 2008 16:29:23 -0500 Message-ID: <47A38F33.9050505@redhat.com> References: <4790C76F.2050105@redhat.com> <47A387D9.1070206@redhat.com> <1201900017.11291.43.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Linux Kernel Mailing List , linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andrew Morton , linux-fsdevel To: Trond Myklebust Return-path: In-Reply-To: <1201900017.11291.43.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.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