From: Ian Kent <raven@themaw.net>
To: Jon Forrest <jlforrest@berkeley.edu>
Cc: autofs@linux.kernel.org
Subject: Re: Transient Automount Problems in CentOS 5.3
Date: Fri, 05 Feb 2010 12:42:52 +0800 [thread overview]
Message-ID: <4B6BA1CC.9020208@themaw.net> (raw)
In-Reply-To: <4B6AFAD1.1070601@berkeley.edu>
On 02/05/2010 12:50 AM, Jon Forrest wrote:
> I have a new cluster running CentOS 5.3.
> The cluster uses a Sun 7310 storage server
> that provides NFS service over a private
> 1Gb/s ethernet with 9K jumbo frames to the
> cluster.
>
> We've noticed that a number of the compute
> nodes sometimes generate the
>
> automount[15023]: umount_autofs_indirect: ask umount returned busy /home
>
> message. When this happens the program running on the
> node dies. This has happened between 10 and 20 times.
> We're not sure what's going on on a node when this
> happens. Most of the time everything is fine and
> the home directories are automounted without problem.
>
> I've googled for this problem and I see that other people
> have seen it too, but I've never seen a resolution,
> especially not for RHEL5.
>
> The auto.master line for this mount is
>
> /home /etc/auto.home --timeout=1200
> noatime,nodiratime,rw,noacl,rsize=32768,wsize=32768
>
> The network interface configuration is
>
> eth0 Link encap:Ethernet HWaddr 00:30:48:B9:F6:52
> inet addr:10.1.255.233 Bcast:10.1.255.255 Mask:255.255.0.0
> inet6 addr: fe80::230:48ff:feb9:f652/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
> RX packets:32999308 errors:0 dropped:0 overruns:0 frame:0
> TX packets:27468315 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:24225053296 (22.5 GiB) TX bytes:73313582546 (68.2 GiB)
> Interrupt:74 Base address:0x2000
>
> The automount is
>
> Linux automount version 5.0.1-0.rc2.102
>
> Directories:
> config dir: /etc/sysconfig
> maps dir: /etc
> modules dir: /usr/lib64/autofs
>
> Compile options:
> DISABLE_MOUNT_LOCKING ENABLE_IGNORE_BUSY_MOUNTS WITH_HESIOD WITH_LDAP
> WITH_SASL
>
> The kernel is 2.6.18-128.1.14.el5.
>
> Any advice on what to do?
Update to 5.4, at least the autofs package and the kernel, and see if
the problem persists.
Ian
next prev parent reply other threads:[~2010-02-05 4:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 16:50 Transient Automount Problems in CentOS 5.3 Jon Forrest
2010-02-04 16:57 ` Carsten Aulbert
2010-02-04 18:09 ` Jon Forrest
2010-02-05 7:59 ` Carsten Aulbert
2010-02-05 17:10 ` Jon Forrest
2010-02-05 17:30 ` Carsten Aulbert
2010-02-05 4:42 ` Ian Kent [this message]
2010-02-05 16:31 ` Jon Forrest
2010-02-05 16:43 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2010-02-04 0:16 Jon Forrest
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B6BA1CC.9020208@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=jlforrest@berkeley.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.