From: Anand Avati Subject: Re: regressions due to 64-bit ext4 directory cookies Date: Thu, 28 Mar 2013 11:49:36 -0700 Message-ID: References: <20130213224720.GE5938@thunk.org> <20130213230511.GW14195@fieldses.org> <20130213234430.GF5938@thunk.org> <5151BD5F.30607@itwm.fraunhofer.de> <5151C33E.2070008@redhat.com> <20130328140744.GA4989@thunk.org> <20130328175205.GD16651@lenny.home.zabbo.net> <20130328183153.GG7080@fieldses.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1773639004856893358==" Cc: Eric Sandeen , linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Theodore Ts'o , Zach Brown , Bernd Schubert , linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, gluster-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org To: "J. Bruce Fields" Return-path: In-Reply-To: <20130328183153.GG7080-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gluster-devel-bounces+gcfgd-gluster-devel=m.gmane.org-qX2TKyscuCcdnm+yROfE0A@public.gmane.org Sender: gluster-devel-bounces+gcfgd-gluster-devel=m.gmane.org-qX2TKyscuCcdnm+yROfE0A@public.gmane.org List-Id: linux-ext4.vger.kernel.org --===============1773639004856893358== Content-Type: multipart/alternative; boundary=001a11c1d64cbe531304d9009db5 --001a11c1d64cbe531304d9009db5 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Mar 28, 2013 at 11:31 AM, J. Bruce Fields wrote: > > > Jeff reported that the approach did not work in his testing. I haven't > had > > a chance to look into the failure yet. Independent of the fix, it would > > certainly be good have the ioctl() support > > The one advantage of your scheme is that it keeps more of the hash bits; > the chance of 31-bit cookie collisions is much higher. Yes, it should, based on the theory of how ext4 was generating the 63bits. But Jeff's test finds that the experiment is not matching the theory. I intend to debug this, but currently drowned in a different issue. It would be good if the ext developers can have a look at http://review.gluster.org/4711 and see if there are obvious holes in the approach or code. Avati --001a11c1d64cbe531304d9009db5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Thu, Mar 28, 2013 at 11:31 AM, J. Bru= ce Fields <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org> wrote:
> Jeff reported that the approach did not work in his testing. I haven&#= 39;t had
> a chance to look into the failure yet. Independent of the fix, it woul= d
> certainly be good have the ioctl() support

The one advantage of your scheme is that it keeps more of the h= ash bits;
the chance of 31-bit cookie collisions is much higher.
Yes, it should, based on the theory of how ext4 was generating = the 63bits. But Jeff's test finds that the experiment is not matching t= he theory. I intend to debug this, but currently drowned in a different iss= ue. It would be good if the ext developers can have a look at http://review.gluster.org/4711 and see if= there are obvious holes in the approach or code.

Avati

--001a11c1d64cbe531304d9009db5-- --===============1773639004856893358== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gluster-devel mailing list Gluster-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org https://lists.nongnu.org/mailman/listinfo/gluster-devel --===============1773639004856893358==--