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