Ok, I found the issue in the end, with a little help from: http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/ So it appears that glusterfs sets an attribute on the path that it adds as a volume. This is nice, but could it remove it again if the volume creation fails? Also, it would be great is the volume create command gave a message like: srv14:/content/sg13/vd00 or a prefix of it is already marked as part of a volume (extended attribute trusted.glusterfs.volume-id exists on /content/sg13/vd00) So we could be pointed in the right direction. Jeff On Aug 9, 2012, at 4:07 PM, Jeff Williams wrote: > Hi, > > There is something strange going on here, and I hoped someone could point me in the right direction: > > srv14# gluster volume create content replica 2 transport tcp srv13:/content/sg13/vd00 srv14:/content/sg13/vd00 > Operation failed on 10.20.20.52 > srv14# gluster volume create content replica 2 transport tcp srv13:/content/sg13/vd00 srv14:/content/sg13/vd00 > /content/sg13/vd00 or a prefix of it is already part of a volume > srv14 # gluster volume list > No volumes present in cluster > > > Any ideas? > > Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20120809/debff91c/attachment.htm>
