From: Lukas Kolbe <lukas@einfachkaffee.de>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: nested automounts: bind and nfs
Date: Wed, 10 Oct 2007 19:02:44 +0200 [thread overview]
Message-ID: <1192035764.20253.5.camel@localhost> (raw)
In-Reply-To: <1192034852.3151.21.camel@raven.themaw.net>
Hello Ian,
> Sure, this may not be the only problem but, having been involved in
> discussions about this a few times over the last year I'm pretty sure
> there is also a race in the NFS client kernel code of the kernel you are
> using.
>
> I'll have a look at the log and the map your using and try and reproduce
> what your seeing.
Thank you very much, I look forward to your findings. If you think it's
a bug in either the kernel or util-linux or nfs-utils, I'll ponder the
distributor from now on.
> Ian
--
Lukas
next prev parent reply other threads:[~2007-10-10 17:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 14:08 nested automounts: bind and nfs Lukas Kolbe
2007-10-01 14:17 ` Lukas Kolbe
2007-10-02 4:53 ` Ian Kent
2007-10-02 10:25 ` Lukas Kolbe
[not found] ` <1191321007.27255.12.camel@localhost>
[not found] ` <1191332917.26331.171.camel@raven.themaw.net>
2007-10-02 14:40 ` Lukas Kolbe
2007-10-10 14:15 ` Lukas Kolbe
2007-10-10 14:34 ` Lukas Kolbe
2007-10-10 15:15 ` Ian Kent
2007-10-10 15:29 ` Lukas Kolbe
2007-10-10 16:47 ` Ian Kent
2007-10-10 17:02 ` Lukas Kolbe [this message]
2007-10-11 8:45 ` Ian Kent
2007-10-11 9:11 ` Ian Kent
2007-10-11 10:49 ` Lukas Kolbe
2007-10-11 11:43 ` Ian Kent
2007-10-11 13:43 ` Success! (was: Re: nested automounts: bind and nfs) Lukas Kolbe
2007-10-11 14:36 ` Ian Kent
2007-10-17 10:19 ` nested automounts: bind and nfs Lukas Kolbe
2007-10-11 3:13 ` Ian Kent
2007-10-11 8:24 ` Lukas Kolbe
2007-10-02 5:03 ` Ian Kent
2007-11-08 16:44 ` Lukas Kolbe
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=1192035764.20253.5.camel@localhost \
--to=lukas@einfachkaffee.de \
--cc=autofs@linux.kernel.org \
--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.