Hi all, Running 3.4.1 on Centos6. I have this issue, I created two xfs filesystem on each of two hosts onode1:/data/glusterfs/kvm1/brick1 onode2:/data/glusterfs/kvm1/brick2 onode1:/data/glusterfs/kvm2/brick1 onode1:/data/glusterfs/kvm2/brick2 The first volume was created successfully # gluster volume create kvm1 replica 2 transport tcp onode1:/data/glusterfs/kvm1/brick1 onode2:/data/glusterfs/kvm1/brick2 When I attempt to create the second volume, I got? # gluster volume create kvm2 replica 2 transport tcp onode1:/data/glusterfs/kvm2/brick1 onode2:/data/glusterfs/kvm2/brick2 volume create: kvm2: failed: /data/glusterfs/kvm2/brick1 or a prefix of it is already part of a volume I'm not sure I follow what the error means.? The 2nd set of filesystems have to mount under a totally different directory structure? Thanks in advance Will -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131226/65212275/attachment.html>
On 12/26/2013 02:24 PM, William Kwan wrote:> Hi all, > > Running 3.4.1 on Centos6. > > I have this issue, I created two xfs filesystem on each of two hosts > onode1:/data/glusterfs/kvm1/brick1 > onode2:/data/glusterfs/kvm1/brick2 > > onode1:/data/glusterfs/kvm2/brick1 > onode1:/data/glusterfs/kvm2/brick2 > > The first volume was created successfully > # gluster volume create kvm1 replica 2 transport tcp > onode1:/data/glusterfs/kvm1/brick1 onode2:/data/glusterfs/kvm1/brick2 > > When I attempt to create the second volume, I got > # gluster volume create kvm2 replica 2 transport tcp > onode1:/data/glusterfs/kvm2/brick1 onode2:/data/glusterfs/kvm2/brick2 > volume create: kvm2: failed: /data/glusterfs/kvm2/brick1 or a prefix > of it is already part of a volume > > I'm not sure I follow what the error means. The 2nd set of > filesystems have to mount under a totally different directory structure? >It means the path to the brick, or some preceding directory up the tree, is marked as being part of a volume, or was part of a volume in the past. From your two commands, you're trying to use the same path twice. In volume kvm1 you use the same two bricks as kvm2. Two volumes cannot use the same bricks. Is there a reason you want two volumes? A more typical use case would be: gluster volume create kvms replica 2 onode1:/data/glusterfs/kvm1/brick1 onode2:/data/glusterfs/kvm1/brick1 onode1:/data/glusterfs/kvm1/brick2 onode2:/data/glusterfs/kvm1/brick2 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131226/f81ec492/attachment.html>
May be it is confusing or I'm using the wrong naming conventions. what I'm actually testing is Each node has one brick for each of glusterfs kvm1 and kvm2 So glusterfs kvm1 will have ??? onode1:/data/glusterfs/kvm1/brick1 ??? onode2:/data/glusterfs/kvm1/brick2 while kvm2 will have two bricks ??? onode1:/data/glusterfs/kvm2/brick1 ??? onode1:/data/glusterfs/kvm2/brick2 On both systems, "brick1" and "brick2" are mount points of xfs file systems Now create volume kvm1 was successful while kvm2 is not. volume create: kvm2: failed: /data/glusterfs/kvm2/brick1 or a prefix of it is already part of a volume Thanks W On Thursday, December 26, 2013 5:24 PM, William Kwan <potatok at yahoo.com> wrote: Hi all, Running 3.4.1 on Centos6. I have this issue, I created two xfs filesystem on each of two hosts onode1:/data/glusterfs/kvm1/brick1 onode2:/data/glusterfs/kvm1/brick2 onode1:/data/glusterfs/kvm2/brick1 onode1:/data/glusterfs/kvm2/brick2 The first volume was created successfully # gluster volume create kvm1 replica 2 transport tcp onode1:/data/glusterfs/kvm1/brick1 onode2:/data/glusterfs/kvm1/brick2 When I attempt to create the second volume, I got? # gluster volume create kvm2 replica 2 transport tcp onode1:/data/glusterfs/kvm2/brick1 onode2:/data/glusterfs/kvm2/brick2 volume create: kvm2: failed: /data/glusterfs/kvm2/brick1 or a prefix of it is already part of a volume I'm not sure I follow what the error means.? The 2nd set of filesystems have to mount under a totally different directory structure? Thanks in advance Will -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131227/8070dbd1/attachment.html>