volgen will generate the files. Its like generating RPC stubs for client and server. You can do that on any machine, actually. Then you take the server and client files and put them on server. The client will fetch specification file from the server. Alternately you can also copy the vol file to the client, without turning on fetch spec. ----- Original Message ----- From: "m roth" <m.roth at 5-cent.us> To: gluster-users at gluster.org Sent: Saturday, March 6, 2010 12:26:43 AM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi Subject: Re: glusterfs-volgen Well, my manager wants me to try to get glusterfs working from the rpms that the CentOS team has, so it's try to get 2.0.8 working. I started to follow Chad's process... and ran into the same thing that started me on this: his glusterfs-volgen has *no* --export-directory in the command. Googling, I found <http://www.cs.cmu.edu/~ewalter/gluster/> which is, in fact, 2.0.8. However, there's things I still don't get. Now, I've installed the server and common on all my nodes. I've only installed common and client on my head node (this is an HPC cluster that I'm building this on). 1) where do I run the glusterfs-volgen command, on the head (client) box, or on each of the servers? 2) if the latter, why does the command offer the option of listing multiple hosts? I have, as the link I posted recommends, symlinked /etc/glusterfs with /usr/local/etc/glusterfs. I've created the directories I want as part of this on each of my nodes, all with the same name. Once I get this part, then I'll get to the client side... mark _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
