<br><br><div class="gmail_quote">On Thu, Mar 28, 2013 at 10:52 AM, Zach Brown <span dir="ltr"><<a href="mailto:zab@redhat.com" target="_blank">zab@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Thu, Mar 28, 2013 at 10:07:44AM -0400, Theodore Ts'o wrote:<br>
> On Tue, Mar 26, 2013 at 10:48:14AM -0500, Eric Sandeen wrote:<br>
> > > We don't have reached a conclusion so far, do we? What about the<br>
> > > ioctl approach, but a bit differently? Would it work to specify the<br>
> > > allowed upper bits for ext4 (for example 16 additional bit) and the<br>
> > > remaining part for gluster? One of the mails had the calculation<br>
> > > formula:<br>
> ><br>
> > I did throw together an ioctl patch last week, but I think Anand has a new<br>
> > approach he's trying out which won't require ext4 code changes. I'll let<br>
> > him reply when he has a moment. :)<br>
><br>
> Any update about whether Gluster can address this without needing the<br>
> ioctl patch? Or should we push the ioctl patch into ext4 for the next<br>
> merge window?<br>
<br>
</div></div>They're testing a work-around:<br>
<br>
<a href="http://review.gluster.org/#change,4711" target="_blank">http://review.gluster.org/#change,4711</a><br>
<br>
I'm not sure if they've decided that they're going to go with it, or<br>
not.<font color="#888888"><br></font></blockquote><div><br></div><div>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 - Samba could use it too, if it wanted.</div>
<div><br></div><div>Avati</div><div><br></div></div>