From: Jon Forrest <jlforrest-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: umount_autofs_indirect: ask umount returned busy CentOS 5.3
Date: Tue, 02 Feb 2010 13:51:09 -0800 [thread overview]
Message-ID: <hka6o2$h2o$1@ger.gmane.org> (raw)
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
Any advice on what to do?
Cordially,
--
Jon Forrest
Research Computing Support
College of Chemistry
173 Tan Hall
University of California Berkeley
Berkeley, CA
94720-1460
510-643-1032
jlforrest-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org
reply other threads:[~2010-02-02 21:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='hka6o2$h2o$1@ger.gmane.org' \
--to=jlforrest-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox