<br><br><div class="gmail_quote">On Thu, Apr 12, 2012 at 7:02 PM, Jeff Darcy wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 04/12/2012 11:51 AM, Alex Florescu wrote:<br>
> (3) The reason you continue to get I/O errors is probably that the xattrs on<br>
> the *parent directory* still indicate pending operations on both sides. You<br>
> can verify this with the following command on each brick:<br>
><br>
> getfattr -d -e hex -n trusted.glusterfs.dht /a<br>
><br>
><br>
> Unfortunately:<br>
> getfattr: /a: Input/output error<br>
> And when running on any working instance, it says trusted.glusterfs.dht: No<br>
> such attribute.<br>
<br>
</div>Oops, my mistake. It appears that the bricks are at /local on each of the<br>
servers, so do the getfattr there.
</blockquote><div> <br>I am sorry to report that getfattr is not returning any information.<br>getfattr -d -e hex -n trusted.gluster.dht /local/howareyou<br>/localh/howareyou: trusted.gluster.dht: No such attribute<br>getfattr -d /local/howareyou<br>
<blank><br><br>mount<br>/dev/sda2 on / type ext4 (rw,user_xattr) - the same on both servers.<br><br>I've recreated the replication volume from scratch and still nothing. I can confirm xattr is working:<br>setfattr -n user.root -v is.xattr.working.? /local/howareyou<br>
getfattr -d /local/howareyou<br>getfattr: Removing leading '/' from absolute path names<br># file: local/howareyou<br>user.root="is.xattr.working.?"<br><br>getfattr -d -n trusted.gluster.dht /local/howareyou<br>
/localh/howareyou: trusted.gluster.dht: No such attribute<br><br></div></div>