Kon,
With Gluster 3.1.1, you no longer need to do anything with the vol files.
If you create a volume like you did below, then you simply mount it like:
mount -t glusterfs 172.16.16.50:/pool /pool/mount
Gluster automatically gets the volume information when mounting. This is
described at:
http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_Manu
ally_Mounting_Volumes
There is no need to do anything with the vol files you found in
/etc/glusterd, and in fact using these can cause some functionality such
as volume elasticity to break.
-Jacob
-----Original Message-----
From: gluster-users-bounces at gluster.org
[mailto:gluster-users-bounces at gluster.org] On Behalf Of Kon Wilms
Sent: Thursday, December 09, 2010 10:24 AM
To: gluster-users at gluster.org
Subject: [Gluster-users] GlusterFS 3.1.1 - local volume mount
What is the desired operation mode for mounting local volumes to
re-export when creating volumes in an automated fashion?
Using gluster to create a new volume automagically does not place any
.vol files in /etc/glusterfs. I'm not sure if this is by design, but
it isn't documented.
Creating a new volume:
gluster volume create pool replica 2 transport tcp
172.16.16.50:/pool/raw 172.16.16.51:/pool/raw 172.16.16.52:/pool/raw
172.16.16.53:/pool/raw
I can mount this as follows:
glusterfs --volfile=/etc/glusterd/vols/pool/pool-fuse.vol /pool/mount
Should I make a local copy of the pool-fuse.vol volume file and place
it in /etc/glusterfs?
Cheers
Kon
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users