All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Waychison <Michael.Waychison@Sun.COM>
To: David Meleedy <david.meleedy@analog.com>
Cc: autofs@linux.kernel.org
Subject: Re: Re: Intermittant problems mounting with automounter
Date: Tue, 14 Dec 2004 19:13:57 -0500	[thread overview]
Message-ID: <41BF81C5.5040205@sun.com> (raw)
In-Reply-To: <200411302007.iAUK7GjH020588@jetcar.spd.analog.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Meleedy wrote:
> Well, in order to troubleshoot this issue further, autofs on Redhat
> Enterprise 3, update 3
> 
> I removed all options from the /etc/auto.master file:
> 
> from:
> 
> /cpd            /etc/auto.cpd  hard,intr,rsize=8192,wsize=8192
> 
> to:
> 
> /cpd            /etc/auto.cpd 
> 
> 
> After this change, the following errors seemed to go away:
> 
> ====
> Nov 19 11:27:38 codered kernel: RPC: Can't bind to reserved port (98).
> Nov 19 11:27:38 codered kernel: nfs_get_root: getattr error = 5
> Nov 19 11:27:38 codered kernel: RPC: Can't bind to reserved port (98).
> Nov 19 11:27:38 codered kernel: nfs_get_root: getattr error = 5
> Nov 19 11:27:38 codered kernel: nfs_read_super: get root inode failed
> Nov 19 11:27:38 codered kernel: nfs warning: mount version older than kernel
> Nov 19 11:27:38 codered kernel: RPC: Can't bind to reserved port (98).
> Nov 19 11:27:38 codered kernel: nfs_get_root: getattr error = 5
> Nov 19 11:27:38 codered kernel: nfs_read_super: get root inode failed
> Nov 19 11:27:38 codered automount[3623]: >> mount: wrong fs type, bad option, 
> bad superblock on aflac:/vol/vol1/cpd/nwd_usr,
> Nov 19 11:27:38 codered automount[3623]: >>        or too many mounted file 
> systems
> Nov 19 11:27:38 codered automount[3623]: mount(nfs): nfs: mount failure 
> aflac:/vol/vol1/cpd/nwd_usr on /cpd/usr
> Nov 19 11:27:38 codered automount[3623]: failed to mount /cpd/usr
> =====
> 
> So whatever it is might be caused by the options?
> 

These messages are due to starvation for reserved ports (< 1024).
Specifically, the kernel will only use ports < 800.  Currently, the
kernel uses one port per nfs filesystem.  If you mount filesystems very
fast, then you can also run out of reserved ports as the local (mountd
iirc?) will close tcp sessions and each must wait 2 minutes before being
released.

One solution is to try out the patch I posted last week that allows nfs
mounts to share tcp/udp connections:

http://marc.theaimsgroup.com/?l=linux-nfs&m=110261671705396&w=2

(against 2.6.9, although should apply to other kernels w/o too much
difficulty)

HTH,

- --
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

iD8DBQFBv4HFdQs4kOxk3/MRAvoxAJ0XCN+p94P2SdOkm9GuLPpiA9CsOQCdEkk/
ljNrkssKI9W/O/QxGjFycYc=
=GF6k
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2004-12-15  0:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 20:07 Intermittant problems mounting with automounter David Meleedy
2004-12-14 14:10 ` Todd Denniston
2004-12-14 23:36   ` David Meleedy
2004-12-15  0:13 ` Mike Waychison [this message]
2004-12-15 15:02   ` Jeff Moyer

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=41BF81C5.5040205@sun.com \
    --to=michael.waychison@sun.com \
    --cc=autofs@linux.kernel.org \
    --cc=david.meleedy@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.