From: Arun Sharma <arun.sharma@intel.com>
To: Ion Badulescu <lists@news.cs.columbia.edu>
Cc: nfs@lists.sourceforge.net, autofs@vger.kernel.org
Subject: Re: VFS: Busy inodes after unmount on 2 way SMP
Date: Fri, 12 Sep 2003 17:08:58 -0700 [thread overview]
Message-ID: <3F62601A.5000105@intel.com> (raw)
In-Reply-To: <200309122333.h8CNXbW09877@moisil.badula.org>
Ion Badulescu wrote:
>
> I don't know if it's the same issue, but I've seen it many many times
> while testing amd's autofs functionality. It occurs when a non-empty
> autofs filesystem is unmounted, e.g. if it has some leftover
> subdirectories from previous mounts. Therefore I'd say it's quite
> clearly an autofs issue, at least in my case.
Do you have a case that can deterministically reproduce the issue ?
> Do you see it when shutting down the automounter, or in other cases as
> well?
Everytime I've seen it, it's during an unmount by /usr/sbin/automount after the mount has expired. It's usually coupled with a temporarily unreachable NFS server.
-Arun
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-09-13 0:08 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 0:11 VFS: Busy inodes after unmount on 2 way SMP Arun Sharma
2003-09-12 1:05 ` H. Peter Anvin
2003-09-12 14:23 ` Ryan Go
2003-09-12 17:57 ` Arun Sharma
2003-09-12 20:51 ` H. Peter Anvin
2003-09-12 23:33 ` Ion Badulescu
2003-09-13 0:08 ` Arun Sharma [this message]
2003-09-13 0:16 ` Ion Badulescu
2003-09-13 0:16 ` Ion Badulescu
2003-09-15 21:42 ` [NFS] " Arun Sharma
2003-09-15 22:25 ` H. Peter Anvin
2003-09-15 22:34 ` Arun Sharma
2003-09-15 23:42 ` Ion Badulescu
2003-09-16 1:34 ` [autofs] " Matt C
2003-09-16 1:34 ` Matt C
2003-09-19 2:57 ` Frank Cusack
2003-09-16 20:37 ` Re: [NFS] " Arun Sharma
2003-09-16 20:54 ` H. Peter Anvin
2003-09-17 0:28 ` Ian Kent
2003-09-17 2:05 ` Arun Sharma
2003-09-17 2:28 ` H. Peter Anvin
2003-09-17 4:56 ` Ian Kent
2003-09-17 4:52 ` Ian Kent
2003-09-17 17:47 ` Arun Sharma
2003-09-17 20:41 ` H. Peter Anvin
2003-09-17 21:00 ` Olaf Hering
2003-09-18 0:31 ` Ian Kent
2003-09-18 5:04 ` Olaf Hering
2003-09-18 5:52 ` Re: [autofs] " Trond Myklebust
2003-09-18 8:26 ` Olaf Kirch
2003-09-19 23:36 ` [NFS] " Olaf Hering
2003-09-25 23:17 ` Re: [autofs] " Matt C
2003-09-25 23:17 ` Matt C
2003-09-26 0:24 ` Trond Myklebust
2003-09-26 0:24 ` Trond Myklebust
2003-09-26 18:31 ` [NFS] " Ion Badulescu
2003-09-26 22:29 ` Re: [autofs] " Trond Myklebust
2003-09-27 16:55 ` Olaf Kirch
2003-09-28 23:16 ` Steve Fosdick
2003-09-29 12:07 ` Ion Badulescu
2003-09-29 17:22 ` Trond Myklebust
2003-09-30 12:50 ` Olaf Kirch
2003-09-30 13:31 ` Trond Myklebust
2003-09-29 3:27 ` Frank Cusack
2003-09-18 2:26 ` [NFS] " Ion Badulescu
2003-09-18 2:54 ` H. Peter Anvin
2003-09-29 12:19 ` Ion Badulescu
2003-09-30 12:24 ` Ian Kent
2003-09-30 12:51 ` Mike Waychison
2003-10-01 12:56 ` Ian Kent
2003-09-30 13:12 ` Ion Badulescu
2003-09-30 16:44 ` Ian Kent
2003-09-17 13:14 ` Ryan Go
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=3F62601A.5000105@intel.com \
--to=arun.sharma@intel.com \
--cc=autofs@vger.kernel.org \
--cc=lists@news.cs.columbia.edu \
--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.