[Gluster-users] Automount using /net/<brickname> in Glusterfs 3.1?

Sat Nov 20 18:02:17 UTC 2010

it's nothing special. whatever comes with redhat. IIRC we have to uncomment the /net but it's done via cfengine, so it's far removed from my memory.

-luis

On Nov 20, 2010, at 11:56 AM, Burnash, James wrote:

> Ah HA! Good to know, Luis.
> 
> Could you possibly share the relevant portions of your auto.master and auto.misc? I just want to confirm that I'm doing things as expected.
> 
> Thanks in advance.
> 
> James
> 
> -----Original Message-----
> From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Luis E. Cerezo
> Sent: Friday, November 19, 2010 8:11 PM
> To: Craig Carl
> Cc: gluster-users at gluster.org
> Subject: Re: [Gluster-users] Automount using /net/<brickname> in Glusterfs 3.1?
> 
> craig, we used the /net method for some testing. the nfs server fell over pretty easily. I've mentioned it to support already.
> 
> 
> On Nov 19, 2010, at 6:18 PM, Craig Carl wrote:
> 
>> James -
>>  Gluster supports the *nix standard method of automounting NFS mounts. You will need to update /etc/auto.master and /etc/auto.misc and restart the autofs service. After that whenever a user or process attempts to access the directory it will be mounted in the background.
>> 
>> Some CentOS documentation - http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-nfs-client-config-autofs.html
>> 
>> Thanks,
>> 
>> Craig
>> 
>> -->
>> Craig Carl
>> Senior Systems Engineer
>> Gluster
>> 
>> On 11/19/2010 12:25 PM, Burnash, James wrote:
>>> Hi Jacob.
>>> 
>>> The link you gave me was the page I was referring to in my post - that's not what I need in terms of function or configuration, so no help to me, unfortunately.
>>> 
>>> What I'm asking for is - what do I need to do on the client to automount a Gluster NFS share without specifically mounting it using the mount command - but instead using /net/<brickname>/<sharename>  syntax to automount and access the directory.
>>> 
>>> This is a crucial part of the client configuration, and cannot be changed in our current environment.
>>> 
>>> Any further help is appreciated.
>>> 
>>> Thanks,
>>> 
>>> James Burnash, Unix Engineering
>>> T. 201-239-2248
>>> jburnash at knight.com | www.knight.com
>>> 
>>> 545 Washington Ave. | Jersey City, NJ
>>> 
>>> 
>>> -----Original Message-----
>>> From: Jacob Shucart [mailto:jacob at gluster.com]
>>> Sent: Thursday, November 18, 2010 6:13 PM
>>> To: Burnash, James; gluster-users at gluster.org
>>> Subject: RE: [Gluster-users] Automount using /net/<brickname>  in Glusterfs 3.1?
>>> 
>>> James,
>>> 
>>> Did you follow the instructions in:
>>> 
>>> http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_Auto
>>> matically_Mounting_Volumes_Using_NFS
>>> 
>>> Please let me know if something in those instructions was not working.
>>> Thank you!
>>> 
>>> -Jacob
>>> 
>>> -----Original Message-----
>>> From: gluster-users-bounces at gluster.org
>>> [mailto:gluster-users-bounces at gluster.org] On Behalf Of Burnash, James
>>> Sent: Thursday, November 18, 2010 9:13 AM
>>> To: gluster-users at gluster.org
>>> Subject: [Gluster-users] Automount using /net/<brickname>  in Glusterfs
>>> 3.1?
>>> 
>>> Hi.
>>> 
>>> I'm running Glusterfs 3.1.01 on Centos 5.2. I have 2 bricks setup as
>>> mirrored and distributed, created using the 3.1 gluster commands. They all
>>> work fine for client mounts and NFS mounts on the client of the form:
>>> mount -t nfs<brickname>:/mytest /mytest.
>>> 
>>> I've gone through all the Gluster documentation about automatic mounting -
>>> /etc/fstab entries, etc. I did find some information on entries needed for
>>> map files - but nothing I've tried has worked for automounting a Glusterfs
>>> NFS share with this syntax:
>>> 
>>> cd /net/<brickname>/mydirectory
>>> 
>>> The command returns successfully, but a subsequent "mount" command shows
>>> that this automount directory is actually writing to "/" on the client.
>>> 
>>> This is the syntax used everywhere in house so that explicit NFS mounts
>>> aren't needed in the /etc/fstab of every machine, and so there is no
>>> dependency on those mounts at boot time.
>>> 
>>> Has anybody tried this syntax, and if so what did you have to configure to
>>> use autofs or amd daemons to perform this activity?
>>> 
>>> James Burnash, Unix Engineering
>>> 
>>> 
>>> DISCLAIMER:
>>> This e-mail, and any attachments thereto, is intended only for use by the
>>> addressee(s) named herein and may contain legally privileged and/or
>>> confidential information. If you are not the intended recipient of this
>>> e-mail, you are hereby notified that any dissemination, distribution or
>>> copying of this e-mail, and any attachments thereto, is strictly
>>> prohibited. If you have received this in error, please immediately notify
>>> me and permanently delete the original and any copy of any e-mail and any
>>> printout thereof. E-mail transmission cannot be guaranteed to be secure or
>>> error-free. The sender therefore does not accept liability for any errors
>>> or omissions in the contents of this message which arise as a result of
>>> e-mail transmission.
>>> NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at
>>> its discretion, monitor and review the content of all e-mail
>>> communications. http://www.knight.com
>>> 
>>> 
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org
>>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>> 
> 
> Luis E. Cerezo
> 
> blog:     http://www.luiscerezo.org
> fotofun: http://www.flickr.com/photos/luiscerezo/
> twitter: http://twitter.com/luiscerezo/
> Voice: +1 412 223 7396
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
> 

Luis E. Cerezo

blog:     http://www.luiscerezo.org
fotofun: http://www.flickr.com/photos/luiscerezo/
twitter: http://twitter.com/luiscerezo/
Voice: +1 412 223 7396