On 08/21/2013 08:21 PM, Stroppa Daniele (strp) wrote:
Thanks Daniel.
I'm indeed running Gluster 3.4 on CentOS 6.4.
I've tried your suggestion, it does work for me too, but it's not an
optimal solution.
Maybe someone could shed some light on this behaviour?
This might be of help in understanding the behavior:
http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/
Please do let us know if you need more clarity on this.
-Vijay
Thanks,
--
Daniele Stroppa
Researcher
Institute of Information Technology
Zürich University of Applied Sciences
http://www.cloudcomp.ch <http://www.cloudcomp.ch/>
On 21/08/2013 09:00, "Daniel Müller" <[email protected]> wrote:
Are you running with gluster 3.4?
I had the same issue. I solved it by deleting my subfolders again and then
create new ones. In your case brick1 and brick2.
Then create new subfolders in the place,ex.: mkdir /mnt/bricknew1 and
/mnt/bricknew2 .
This solved the problem for me, not knowing why gluster 3.4 behave like
this.
Good Luck
EDV Daniel Müller
Leitung EDV
Tropenklinik Paul-Lechler-Krankenhaus
Paul-Lechler-Str. 24
72076 Tübingen
Tel.: 07071/206-463, Fax: 07071/206-499
eMail: [email protected]
Internet: www.tropenklinik.de
Von: [email protected]
[mailto:[email protected]] Im Auftrag von Stroppa Daniele
(strp)
Gesendet: Dienstag, 20. August 2013 21:51
An: [email protected]
Betreff: [Gluster-users] Volume creation fails with "prefix of it is
already
part of a volume"
Hi All,
I'm setting up a small test cluster: 2 nodes (gluster-node1 and
gluster-node4) with 2 bricks each (/mnt/brick1 and /mnt/brick2) and one
volume (vol_icclab). When I issue the create volume command I get the
following error:
# gluster volume create vol_icclab replica 2 transport tcp
gluster-node4.test:/mnt/brick1/vol_icclab
gluster-node1.test:/mnt/brick1/vol_icclab
gluster-node4.test:/mnt/brick2/vol_icclab
gluster-node1.test:/mnt/brick2/vol_icclab
volume create: vol_icclab: failed: /mnt/brick1/vol_icclab or a prefix of
it
is already part of a volume
I checked and found this [1], but in my case the issue it's happening when
creating the volume for the first time, not after removing/adding a brick
to
a volume.
Any suggestions?
[1]
http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-p
art-of-a-volume/
Thanks,
--
Daniele Stroppa
Researcher
Institute of Information Technology
Zürich University of Applied Sciences
http://www.cloudcomp.ch
_______________________________________________
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
