All of lore.kernel.org
 help / color / mirror / Atom feed
From: robsims@robsims.com (Rob Sims)
To: autofs@linux.kernel.org
Subject: Re: Re: BUG: autofs4 + cd /net/<Netapp>/vol/vol[0-3] = port usage problems
Date: Mon, 29 Aug 2005 09:20:50 -0600	[thread overview]
Message-ID: <20050829152050.GA28102@robsims.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0508271125440.2069@donald.themaw.net>

On Sat, Aug 27, 2005 at 11:34:09AM +0800, Ian Kent wrote:
> The attempt to remount on umount fail has always been a contentious in my 
> opinion, however I`ve yet to see a situation that hasn't been caused by 
> something else that needs to be fixed.

I agree - remounting something that is already mounted should be a no-op
in the nfs system.

> I thought I asked for versions?
> Can we have`em.

Sorry - locally-compiled kernel 2.4.23, using autofs4 as a module.
Debian packaging of autofs, 3.9.99-4.0.0pre10-1.  Have unconfirmed
sightings on kernel 2.6.8, autofs 4.1.3+4.1.4beta2-10.  I don't think
these sightings are credible.  No reports since dropping the number of
exports.

> If neccessary looking at the code will tell if you have what's needed to 
> avoid this. Send me a copy of parse_sun.c from the source you are using 
> and I'll check.

I'm using the Debian woody package.  The following is from the source
package after unpacking and building (which applies any patches).
http://www.robsims.com/parse_sun.c

I'll poke around the source some more.  What I want to know is:
1) Are all the child mounts unmounted before unmounting the parent?
2) If not, were the system calls successful?
3) If the system calls failed, what were the error codes?
4) If all child mounts were in fact unmounted, why is the parent busy?

I'll write back what I find, but may not have time for serious digging
for the next couple of weeks.
-- 
Rob

  reply	other threads:[~2005-08-29 15:20 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
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 [this message]
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=20050829152050.GA28102@robsims.com \
    --to=robsims@robsims.com \
    --cc=autofs@linux.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 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.