From: "David B. Ritch" <dritch@hpti.com>
To: NFS mailing list <nfs@lists.sourceforge.net>
Cc: Craig Tierney <ctierney@hpti.com>
Subject: NFS mount/umount problem
Date: 16 Jan 2003 14:17:36 -0500 [thread overview]
Message-ID: <1042744656.3312.43.camel@localhost> (raw)
A colleague of mine who is having email difficulties asked me to forward
this to the list.
I am having a problem with nfs mounts under linux-2.4.20.
Server:
Redhat-8.0, kernel upgraded to linux-2.4.20 + Trond's NFS Patches.
Dual PIII 933 Mhz, 2 GB ram, tg3 gigabit ethernet driver.
Client
Redhat-7.1, kernel upgraded to linux-2.4.18 + Trond's NFS patches.
Dual Xeon 2.2 Ghz, 1 GB ram, e100 ethernet driver.
After I upgraded the server from 2.4.14 to 2.4.20, I am having a problem
mounting and unmounting the NFS partitions using autofs. I have all
of the clients touch the nfs filesystems (ls /misc/scratchx) to cause
them to mount. Many of the mounts fail (~ 50%) with the error. If I
slow
down the rate at which the ls is executed, I have a better chance at
mounting all of the filesystems. When I operate on chucks of the nodes
128 at a time, I can usually get them to mount ok.
In the messages file I get:
Jan 16 16:58:51 g0427 automount[537]: attempting to mount entry
/misc/scratchx
Jan 16 16:59:12 g0427 automount[13130]: >> mount: RPC: Timed out
Jan 16 16:59:12 g0427 automount[13130]: mount(nfs): nfs: mount failure
x00:/export/scratch1 on /misc/scratchx
I tried increasing timeo to 30 and 60, and this appeared to help it
did not fix the problem. I never change timeo before.
When the mounts do fail, I try and clean them up with umount. Often
when doing this I will get error messages on some of the nodes:
Bad UMNT RPC: RPC: Timed out
This problem can be reduced when I do not have the umount execute on
all of the nodes at the same time.
This happens with when the filesystem is ext3 or xfs.
I do not have these problems under the 2.4.14 kernel.
Are there some timing values in RPC that have changed or that I can
change
to increase timeouts? Does anyone have any other ideas?
Thanks,
Craig
--
David B. Ritch
High Performance Technologies, Inc.
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-01-16 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 19:17 David B. Ritch [this message]
2003-01-16 20:00 ` NFS mount/umount problem Greg Lindahl
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 22:00 Heflin, Roger A.
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=1042744656.3312.43.camel@localhost \
--to=dritch@hpti.com \
--cc=ctierney@hpti.com \
--cc=nfs@lists.sourceforge.net \
/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.