From: "H. Peter Anvin" <hpa@zytor.com>
To: Ion Badulescu <ionut@badula.org>
Cc: nfs@lists.sourceforge.net, autofs@linux.kernel.org,
trond.myklebust@fys.uio.no, james-p@moving-picture.com
Subject: Re: Re: [autofs] Server/client mismatch over status of a mount ...
Date: Wed, 19 Feb 2003 19:16:12 +0100 [thread overview]
Message-ID: <3E53C9EC.8080903@zytor.com> (raw)
In-Reply-To: <200302191358.h1JDwECX026719@buggy.badula.org>
Ion Badulescu wrote:
>
> Isn't autofs v4 supposed to fix this? I remember Jeremy mentioning that
> the filesystem would lock all accesses to a dentry scheduled to be
> unmounted until the daemon replied to the request.
>
That's fine and dandy, but you would have to atomically lock *all*
dentries belonging to the subtree, which I suspect (but don't know for
sure) is impossible.
-hpa
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-19 18:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 14:06 Server/client mismatch over status of a mount James Pearson
2003-02-17 15:20 ` [autofs] " H. Peter Anvin
2003-02-17 15:50 ` Trond Myklebust
2003-02-17 15:57 ` James Pearson
2003-02-17 16:16 ` Trond Myklebust
2003-02-17 17:49 ` James Pearson
2003-02-18 16:57 ` James Pearson
2003-02-19 9:56 ` H. Peter Anvin
2003-02-19 10:16 ` Trond Myklebust
2003-02-19 13:58 ` Ion Badulescu
2003-02-19 18:16 ` H. Peter Anvin [this message]
2003-02-20 3:20 ` Jeremy Fitzhardinge
2003-02-20 3:26 ` Ion Badulescu
2003-02-20 3:43 ` Jeremy Fitzhardinge
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=3E53C9EC.8080903@zytor.com \
--to=hpa@zytor.com \
--cc=autofs@linux.kernel.org \
--cc=ionut@badula.org \
--cc=james-p@moving-picture.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.