[Gluster-devel] regressions due to 64-bit ext4 directory cookies

John Mark Walker johnmark at redhat.com
Wed Feb 13 14:06:14 UTC 2013

[forwarding from Ted T'so whose email was rejected by our mailing list. -JM]

Date: Tue, 12 Feb 2013 23:00:03 -0500
From: Theodore Ts'o <tytso at mit.edu>
To: "J. Bruce Fields" <bfields at fieldses.org>
Cc: linux-ext4 at vger.kernel.org, sandeen at redhat.com, Bernd Schubert
 <bernd.schubert at itwm.fraunhofer.de>, gluster-devel at nongnu.org
Subject: Re: regressions due to 64-bit ext4 directory cookies

On Tue, Feb 12, 2013 at 03:28:41PM -0500, J. Bruce Fields wrote:
> 06effdbb49af5f6c "nfsd: vfs_llseek() with 32 or 64 bit offsets (hashes)"
> and previous patches solved problems with hash collisions in large
> directories by using 64- instead of 32- bit directory hashes in some
> cases.  But it caused problems for users who assume directory offsets
> are "small".  Two cases we've run across:
>         - older NFS clients: 64-bit cookies cause applications on many
>           older clients to fail.

Is there a list of clients (and version numbers) which are having

> A "no_64bit_cookies" export option would provide a workaround for NFS
> servers with older NFS clients, but not for applications like gluster.

Why isn't it sufficient for gluster?  Are they doing something
horrible such as assuming that telldir() cookies accessed from
userspace are identical to NFS cookies?  Or is it some other horrible
abstraction violation?

                                                - Ted

More information about the Gluster-devel mailing list