On 08/09/2012 07:56 PM, Jeff Williams wrote: > 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) > Thanks, this sounds more like how we want the message to be. Can you please open a bug? We'll have it addressed in an upcoming release. -Vijay