<div class="gmail_quote">On Fri, Apr 13, 2012 at 4:05 PM, Rodrigo Severo <span dir="ltr"></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"><div class="gmail_quote"><div class="gmail_quote"><div>You are using <i>-d</i> and <i>-n</i> on the same getfattr. That's wrong AFAICT.<br><br>Try <i>getfattr -d -m . -e hex -h BRICK/PATH/TO/FILE/OR/DIRECTORY<br>
<br></i>You should get a full list of extended attributes related to the file/directory.<span><font color="#888888"><br></font></span></div></div></div></div></div></blockquote><div><br>Yes, now it's working. Thank you.<br>
So, for the previous scenario described already:<br>> Simulation follows:<br>> step 1<br>> node1:<br>> iptables -I INPUT 1 -s 10.0.2.15 -j DROP (connectivity loss simulation)<br>> touch /a/howareyou<br>> <br>
> node2:<br>> touch /a/hello<br>> <br>> step 2<br>> node1:<br>> iptables -D INPUT 1 (connectivity recovery)<br>> ls /a<br>> ls: cannot access /a: Input/output error<br>> <br>> node2:<br>> ls /a<br>
> ls: cannot access /a: Input/output error<br><br>node1:<br>getfattr -d -m . -e hex /local/<br># file: local/<br>trusted.afr.vol-replication-client-0=0x000000000000000000000000<br>trusted.afr.vol-replication-client-1=0x000000000000000000000001<br>
<br>getfattr -d -m . -e hex /local/howareyou<br># file: local/howareyou<br>trusted.afr.vol-replication-client-0=0x000000000000000000000000<br>trusted.afr.vol-replication-client-1=0x000000000000000100000000<br><br>node2:<br>
getfattr -d -m . -e hex /local/<br># file: local/<br>trusted.afr.vol-replication-client-0=0x000000000000000000000001<br>trusted.afr.vol-replication-client-1=0x000000000000000000000000<br><br>getfattr -d -m . -e hex /local/hello<br>
# file: local/hello<br>trusted.afr.vol-replication-client-0=0x000000000000000100000000<br>trusted.afr.vol-replication-client-1=0x000000000000000000000000<br><br><br>On Fri, Apr 13, 2012 at 4:32 PM, Jeff Darcy wrote:<br>
> Try changing "trusted.gluster.dht" to "trusted.glusterfs.dht" as had<br>
> originally been suggested. Alternatively, you could just use "-m ."<br>
> instead of "-n trusted.gluster.dht" to dump *all* xattrs, and see what<br>> we get.<br><br>No .dht attribute, only afr as you can see.<br><br>> 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.<br><br>Indeed, this is as you said.<br></div></div>