Did u see this? http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/
Am 13.03.2014 17:39:10, schrieb Kent Nasveschuk: > CentOS 6.5, repo glusterfs-epel.repo > I used both of these as guide to upgrade > http://vbellur.wordpress.com/2013/07/15/upgrading-to-glusterfs-3-4/ > http://vbellur.wordpress.com/2012/05/31/upgrading-to-glusterfs-3-3 > My problem seems to be with trusted.glusterfs.volume-id that the 3.2.7 > version doesn't use > I can't seem to set the hex value using any recommendations from previous > posts. There seems to be a bug with this. > For each brick: > ex. setfattr -n trusted.glusterfs.volume-id -v > 0x925ba82b-3a69-431e-a113-e99df3fa1594 /data02a (and the others) > The above doesn't work "bad input encoding" also \0x > I can only get it to take ascii, at which point I can't start the volume, > complains: "Failed to get extended attribute trusted.glusterfs.volume-id for > ...... Numerical result out of range" > Is there a workaround for this? Delete volume add bricks back? Any help would > be appreciated. > Kent > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
