<br><br><div class="gmail_quote">On Thu, Mar 28, 2013 at 11:31 AM, J. Bruce Fields <span dir="ltr"><<a href="mailto:bfields@fieldses.org" target="_blank">bfields@fieldses.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">
> Jeff reported that the approach did not work in his testing. I haven't had<br>
> a chance to look into the failure yet. Independent of the fix, it would<br>
> certainly be good have the ioctl() support<br>
<br>
</div></div>The one advantage of your scheme is that it keeps more of the hash bits;<br>
the chance of 31-bit cookie collisions is much higher.</blockquote><div><br></div><div>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 <a href="http://review.gluster.org/4711">http://review.gluster.org/4711</a> and see if there are obvious holes in the approach or code.</div>
<div><br></div><div>Avati</div><div><br></div></div>