Re: [Users] oVirt 3.1 -- GlusterFS 3.3
On 06/25/2012 10:51 PM, Nathan Stratton wrote:
On Mon, 25 Jun 2012, Robert Middleswarth wrote:
>> I now have a happy gluster volume called share. Now I am lost as to
>> how to use that volume. Do I have to change the Default NFS storage
>> type? How do I get this bad boy mounted?
> I spent 2 weeks tiring to get glusterfs working with no luck. However
> I was able to get gluster nfs working. Here are the steps I needed
> to do.
Are there any docs on direct gluster?
No. I got close to getting it to work but I
was having issues with
Fedora 17 crashing every 10 to 12 hours and that might have been why I
couldn't get that last 1%. I did pretty much the same steps to get
really close to getting the glusterfs structure to work.
1) Mount the volume outside of ovirt. mount -t nfs
ipofonenode:/volumename /temp/share/name or mount -t glusterfs
ipofonenode:/volumename /temp/share/name
2) chown -R 36.36 /temp/share/name
3) umount /temp/share/name
4) Added a new Postfix gluster fs domain with the Path of:
localhost:/volumename and the type of glusterfs.
It mounted fine but I couldn't get it to activate.
> 1) I added the following option to the volume. Might only need
the
> 1st one but I have all 3 of them set on my working system.a) nfs.nlm off
> b) nfs.register-with-portmap on
> c) nfs.addr-namelookup off
> 2) Mount the volume outside of ovirt. mount -t nfs
> ipofonenode:/volumename /temp/share/name
> 3) chown -R 36.36 /temp/share/name.
> 4) umount /temp/share/name
> 5) Added a new NFS domain with the NFS Export Path:
> localhost:/volumename
>
> I was then able to active the NFS based Data Center and add working VM's
Problme I am running into is that I need to add -o
mountproto=tcp,vers=3 because it looks like it is defaulting to udp
and gluster NFS does not support that.
Try editing file /etc/nfsmount.conf on each
node and add the following.
[ NFSMount_Global_Options ]
Defaultvers=3
Nfsvers=3
Thanks
Robert
> <>
Nathan Stratton
nathan at robotics.net
http://www.robotics.net