From: Mike Waychison <Michael.Waychison@Sun.COM>
To: "William.Crocker" <william.crocker@analog.com>
Cc: autofs@linux.kernel.org
Subject: Re: Newbie needs help with automounter.
Date: Mon, 11 Oct 2004 13:11:42 -0400 [thread overview]
Message-ID: <416ABECE.2010701@sun.com> (raw)
In-Reply-To: <200410100037.i9A0bA020600@novus.adsdesign.analog.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
William.Crocker wrote:
> Hello:
>
> I am new to autofs/automounter and need help understanding
> the following messages which I found in /var/log/messages.
>
> These messages appeared when I tried to
> change directory to /proj/asic on cfl30.
>
> If I stop and then start autofs it will work for a while
> and then start failing again.
>
> Thanks in advance.
>
> Bill
>
> ------------- /var/log/messages -------------
>
> Oct 9 18:30:31 cfl30 kernel: RPC: Can't bind to reserved port (98).
> Oct 9 18:30:31 cfl30 kernel: NFS: cannot create RPC transport.
> Oct 9 18:30:31 cfl30 kernel: nfs warning: mount version older than kernel
> Oct 9 18:30:31 cfl30 kernel: RPC: Can't bind to reserved port (98).
> Oct 9 18:30:31 cfl30 kernel: NFS: cannot create RPC transport.
> Oct 9 18:30:31 cfl30 automount[14622]: >> mount: wrong fs type, bad option, bad superblock on 831ntap:/vol/vol0/proj/asic,
> Oct 9 18:30:31 cfl30 automount[14622]: >> or too many mounted file systems
> Oct 9 18:30:31 cfl30 automount[14622]: mount(nfs): nfs: mount failure 831ntap:/vol/vol0/proj/asic on /proj/asic
> Oct 9 18:30:31 cfl30 automount[14622]: failed to mount /proj/asic
> Oct 9 18:30:31 cfl30 kernel: RPC: Can't bind to reserved port (98).
> Oct 9 18:30:31 cfl30 kernel: NFS: cannot create RPC transport.
> Oct 9 18:30:31 cfl30 kernel: nfs warning: mount version older than kernel
> Oct 9 18:30:31 cfl30 kernel: RPC: Can't bind to reserved port (98).
> Oct 9 18:30:31 cfl30 automount[14624]: >> mount: wrong fs type, bad option, bad superblock on 831ntap:/vol/vol0/proj/asic,
> Oct 9 18:30:31 cfl30 kernel: NFS: cannot create RPC transport.
> Oct 9 18:30:31 cfl30 automount[14624]: >> or too many mounted file systems
> Oct 9 18:30:31 cfl30 automount[14624]: mount(nfs): nfs: mount failure 831ntap:/vol/vol0/proj/asic on /proj/asic
> Oct 9 18:30:31 cfl30 automount[14624]: failed to mount /proj/asic
>
This occurs when the kernel can't bind to a reserved port (<1024) when
building the rpc transport. In fact, the rpc code further limits the
available ports to 1-800. You can try upping the value of
XPRT_MAX_RESVPORT in net/sunrpc/xprt.c to 1024, or higher if your nfs
servers don't care what port the client is connecting from.
This said, this is likely a symptom of one of two things:
- - You are mounting hundreds of nfs filesystems (the current code does
not multiplex rpc connections at all).
- - Automounter ran wild and is mounting filesystems that are not getting
freed/umounnted properly.
Can you post the output of 'cat /proc/mounts' and 'netstat -a --inet' as
well as versioning information for your kernel and automounter you are
using?
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBar7NdQs4kOxk3/MRAmKVAKCbxhhMthZ+T2fLG9XZ4Y04+0V1gwCfQ6IQ
oBaXn6tijYWEgbArqoSTlG8=
=LBX8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-10-11 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 0:37 Newbie needs help with automounter William.Crocker
2004-10-11 17:11 ` Mike Waychison [this message]
2004-10-11 17:19 ` Jeff Moyer
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 18:25 Burke, Alan
2004-10-11 18:32 ` Mike Waychison
2004-10-11 18:27 Burke, Alan
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=416ABECE.2010701@sun.com \
--to=michael.waychison@sun.com \
--cc=autofs@linux.kernel.org \
--cc=william.crocker@analog.com \
/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.