<div dir="ltr"><br><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span><font color="#888888"><font><font size="1"><span style="color:rgb(51,51,51)"><span style="color:rgb(153,153,153)"><a value="+17086132426"><font color="#888888"><font size="1"><br></font></font></a></span></span></font></font></font></span></div></div></div></div>
<br><div class="gmail_quote">On Fri, Jul 22, 2016 at 8:12 AM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">2016-07-22 1:54 GMT-04:00 Frank Rothenstein <<a href="mailto:f.rothenstein@bodden-kliniken.de">f.rothenstein@bodden-kliniken.de</a>>:<br>
> The point is that even if all other backend storage filesystems do correctly<br>
> untill 3.7.11 there was no error on ZFS. Something happened nobody ever<br>
> could explain in the release of 3.7.12 that makes FUSE-mount _in ovirt_ (it<br>
> partly uses dd with iflag=direct , using iflag=direct yourself gives also<br>
> errors on the FUSE-mounts ) unusable.<br>
><br>
> So 3.7.11 is the last usable version when using ZFS on bricks, afaik.<br>
><br>
<br>
Can you please share the exact dd command that causes this problem?<br></blockquote><div><br></div><div>I want to say it was this one though my logs for vdsm going back that far have rolled off</div><div><br></div><div> /usr/bin/dd if=/rhev/data-center/mnt/glusterSD/ccgl1.gl.local:GLUSTER1/7c73a8dd-a72e-4556-ac88-7f6813131e64/dom_md/metadata iflag=direct of=/dev/null bs=4096 count=1<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Thanks,<br>
Vijay<br>
</blockquote></div><br></div></div>