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, Ian Kent <raven@themaw.net>
Subject: Re: BUG: autofs4 + cd /net/<Netapp>/vol/vol[0-3] = port usage problems
Date: Wed, 12 Jan 2005 20:05:42 -0500	[thread overview]
Message-ID: <41E5C966.8050108@sun.com> (raw)
In-Reply-To: <200501130037.j0D0bNDj012842@jetcar.spd.analog.com>

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

David Meleedy wrote:
> Mike,
> 	I just recompiled my kernel with your xprt-sharing.patch.
> Although this did fix the port error problems, it did not fix
> the automounter problem.  So I think your patch should be incorporated
> into Redhat Enterprise 3 (2.4 kernel) because it appears to work.


There is a bit of hold-back from the NFS guys for getting this included
mainstream (what Red Hat does is their own business of course).

The reason does make sense.. there is a static number of request slots
available per transport session in the current rpc code.  Translated:
Only 16 io's are capable of being in flight for a given tcp stream with
this patch.

There is concern that this may impact performance numbers for NFS,
though I haven't yet seen hard numbers.  The good news is that there has
been extensive work done as well to allow for dynamic scaling of the
available request slots as part of the rpc transport switch code
happening at UMich.  I haven't had the chance to play with it though and
don't know if it is ready for prime time.  The likelyhood of it ever
making its way into RHEL3 is pretty low, but I can't speak for others.

> 
> I think the problem is that the automounter just cannot unmount
> the /net/aflac directory, and ends up trying to remount it instead,
> here are the log files after the port patch that Mike gave me:
> (this is during the reboot after cd'ing to /net/aflac/vol/vol2)
> 
> Jan 12 19:23:36 codered automount[5396]: can't shutdown: filesystem /net still 
> busy
> Jan 12 19:23:38 codered autofs: automount -USR2 succeeded
> Jan 12 19:23:41 codered automount[5396]: can't shutdown: filesystem /net still 
> busy
> ... those lines keep repeating until ....
> 
> Jan 12 19:24:08 codered automount[16092]: >> mount table full
> Jan 12 19:24:08 codered automount[16092]: mount(nfs): nfs: mount failure 
> aflac:/vol/vol3/cad_archive on /net/aflac/vol/vol3/cad_archive
> Jan 12 19:24:08 codered automount[16092]: >> mount table full
> Jan 12 19:24:08 codered automount[16092]: mount(nfs): nfs: mount failure 
> aflac:/vol/vol3/design on /net/aflac/vol/vol3/design
> ... those lines repeart for each subdirectory of the volumes ...
> 
> Jan 12 19:24:09 codered autofs: automount shutdown failed
> 
> As you can see, it keeps trying to unmount /net, and eventually
> fills up the mount table because it instead remounts it.  Before,
> when the port issue was a problem, it wouldn't get far enough to
> fill the mount table, but now it can (thanks Mike!)
> 
> -Dave
> 
> ________________________________________________________________________
> David Meleedy				Analog Devices, Inc.
> David.Meleedy@analog.com		Three Technology Way
> Phone: 781 461 3494			Norwood, MA  02062-9106  USA
> 
> 


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

iD8DBQFB5clmdQs4kOxk3/MRAo8LAJ9ud4FiaaXKEM9wdQQqyBxegiz8AQCeNvFF
+ZRiL2/tnbqd5BT78pFrAf4=
=aNy9
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-01-13  1:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 21:22 BUG: autofs4 + cd /net/<Netapp>/vol/vol[0-3] = port usage problems David Meleedy
2005-01-12  5:38 ` Ian Kent
2005-01-12 16:55   ` Mike Waychison
2005-01-12 20:43     ` David Meleedy
2005-01-13  0:37     ` David Meleedy
2005-01-13  1:05       ` Mike Waychison [this message]
2005-01-13  1:07       ` Ian Kent
2005-01-14 14:35       ` raven
2005-01-14 22:38         ` David Meleedy
2005-01-15  2:50           ` raven
2005-01-17 14:52             ` Jeff Moyer
2005-01-18  1:31               ` Ian Kent
2005-01-18 14:18                 ` Jeff Moyer
2005-01-18 17:00                   ` Ian Kent
2005-01-18 17:05                     ` Jeff Moyer
2005-01-19  1:25                       ` Ian Kent
2005-01-18 14:20                 ` Jeff Moyer
2005-01-18 17:04                   ` Ian Kent
2005-01-18 17:07                     ` Jeff Moyer
2005-01-18 17:32                     ` Mike Waychison
2005-01-19  4:21                       ` Ian Kent
2005-01-19  5:00                         ` Re: [autofs] " Trond Myklebust
2005-01-17 14:01         ` raven
2005-01-17 16:19           ` David Meleedy
2005-01-18  1:33             ` Ian Kent
2005-01-13  8:13     ` Ian Kent
2005-01-12 14:50 ` raven
2005-01-12 22:22   ` David Meleedy
2005-01-12 23:01     ` Jeff Moyer
2005-01-12 16:13 ` Dwight Marzolf
2005-01-12 20:55   ` David Meleedy
2005-08-25 22:14 ` Rob Sims
2005-08-26  3:44   ` Ian Kent
2005-08-26 16:14     ` Rob Sims
2005-08-27  3:34       ` Ian Kent
2005-08-29 15:20         ` Rob Sims
2005-08-30  1:16           ` Ian Kent

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=41E5C966.8050108@sun.com \
    --to=michael.waychison@sun.com \
    --cc=autofs@linux.kernel.org \
    --cc=david.meleedy@analog.com \
    --cc=raven@themaw.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.