Bug 762775 (GLUSTER-1043) - autofs access hangs
Summary: autofs access hangs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1043
Product: GlusterFS
Classification: Community
Component: core
Version: 3.0.5
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-02 10:55 UTC by Csaba Henk
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Comment 1 Csaba Henk 2010-07-02 10:55:15 UTC
Setting up autofs as follows:

$ cat /etc/auto.master
/auto/gfs /etc/auto.glusterfs 
$ cat /etc/auto.glusterfs
simple     -fstype=glusterfs,log-level=DEBUG,log-file=/tmp/g.log               :/etc/glusterfs/simple.vol
$ cat /etc/glusterfs.simple.vol
volume ex0
  type storage/posix
  option directory /tmp/gex0
end-volume

and then firing up automount results in "ls /etc/auto/simple" hanging.

Reproduced on Ubuntu 10.4 and Arch 2010.5.

Comment 2 Csaba Henk 2010-07-24 06:15:28 UTC
Glusterfs-vs-autofs problems were noticed long ago. It was found out that the problem is with daemonization -- ie. original glusterfs process terminates prior to mounting completed. With autofs4, it was sufficient to have the original process wait for mounting (cf. commit 7e6c9643); with autofs5, this is not enough, autofs5 wants the process spawned by it to do the mount. 

The refacorization of main() done for dynamic volume management solves this issue nicely, by putting fuse init before daemonization. So in mainline, this is FIXED.

For release-3.0 issue is present, patch is sent to fix it up.

Comment 3 Anand Avati 2010-07-29 03:58:21 UTC
PATCH: http://patches.gluster.com/patch/3890 in release-3.0 (make glusterfs work with autofs5)

Comment 4 Amar Tumballi 2010-10-05 06:07:42 UTC
Autofs works fine on 3.1 branch. will be closing the bug.


Note You need to log in before you can comment on or make changes to this bug.