Some of my bricks show no volume xattr at all. Why would that be? What's the downside? [root at dsdb1 gluster]# getfattr -dm - /data2/gluster getfattr: Removing leading '/' from absolute path names # file: data2/gluster trusted.afr.stress-volume-client-16=0sAAAAAAAAAAAAAAAA trusted.afr.stress-volume-client-17=0sAAAAAAAAAAAAAAAA trusted.gfid=0sAAAAAAAAAAAAAAAAAAAAAQ== trusted.glusterfs.dht=0sAAAAAQAAAAB////+lVVVUg== trusted.glusterfs.test="working\000" [root at dsdb3 ~]# ls /data2/gluster/12657/372657 /data2/gluster/12657/372657 [root at dsdb3 ~]# getfattr -dm - /data2/gluster getfattr: Removing leading '/' from absolute path names # file: data2/gluster trusted.gfid=0sAAAAAAAAAAAAAAAAAAAAAQ== trusted.glusterfs.dht=0sAAAAAQAAAACVVVVTqqqqpw== trusted.glusterfs.test="working\000" [root at dsdb4 ~]# ls /data2/gluster/12657/372657 /data2/gluster/12657/372657 [root at dsdb4 ~]# getfattr -dm - /data2/gluster getfattr: Removing leading '/' from absolute path names # file: data2/gluster trusted.gfid=0sAAAAAAAAAAAAAAAAAAAAAQ== trusted.glusterfs.dht=0sAAAAAQAAAACVVVVTqqqqpw== trusted.glusterfs.test="working\000"
