[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20130214214744.GC8343@fieldses.org>
Date: Thu, 14 Feb 2013 16:47:44 -0500
From: "J. Bruce Fields" <bfields@...ldses.org>
To: Anand Avati <anand.avati@...il.com>
Cc: Theodore Ts'o <tytso@....edu>,
Bernd Schubert <bernd.schubert@...m.fraunhofer.de>,
sandeen@...hat.com, linux-nfs@...r.kernel.org,
linux-ext4@...r.kernel.org, gluster-devel@...gnu.org
Subject: Re: [Gluster-devel] regressions due to 64-bit ext4 directory cookies
On Wed, Feb 13, 2013 at 04:05:01PM -0800, Anand Avati wrote:
> On Wed, Feb 13, 2013 at 3:44 PM, Theodore Ts'o <tytso@....edu> wrote:
> >
> > I suspect this would seriously screw over Gluster, though, and this
> > wouldn't be a solution for NFSv3, since NFS needs long-lived directory
> > cookies, and not the short-lived cookies which is all POSIX/SuSv3
> > guarantees.
> >
>
> Actually this would work just fine with Gluster. Except in the case of
> gluster-NFS, the native client is only acting like a router/proxy of
> syscalls to the backend system. A directory opened by an application will
> have a matching directory fd opened on ext4, and readdir from an app will
> be translated into readdir on the matching fd on ext4. So the
> app-on-glusterfs and glusterfsd-on-ext4 are essentially "moving in tandem".
> As long as the offs^H^H^H^H cookies do not overflow in the transformation,
> Gluster would not have a problem.
>
> However Gluster-NFS (and NFS in general, too) will break, as we
> opendir/closedir potentially on every request.
Yes. And, of course, NFS cookies live forever--we have no idea when a
client will hand one back to us and expect us to do something with it.
--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists