From: Ian Kent <raven@themaw.net>
To: Timo Wendt <twendt@online.de>
Cc: autofs@linux.kernel.org
Subject: Re: autofs 5 not recognizing manual umounts properly
Date: Mon, 30 Oct 2006 14:35:02 +0800 [thread overview]
Message-ID: <1162190102.2900.13.camel@localhost> (raw)
In-Reply-To: <B2E30F3E-200F-4D99-8813-732B62601D43@online.de>
On Sat, 2006-10-28 at 18:41 +0200, Timo Wendt wrote:
> Hi,
>
>
> I have just installed FC6 to do some tests with autofs 5 as I need to
> use direct mounts. The new version works really great. The only thing
> I figured out so far that does not work fine is, when I umount one of
> the automounted fs manually.
> If I then try to list the contents of that directory it says, that it
> is empty. As soon as I try to create a file in that directory, it
> fails and seems to realize, that the directory should be mounted and
> remounts it, without creating the file though.
>
>
> Now I have 2 questions:
>
>
> 1. Why is it not remounting the FS when trying an ls on it?
>
>
> 2. Why is it not creating the file after remounting the FS instead of
> failing first and then doing the mount?
I'd need a debug log to see what's going on and more information about
the automount map and the map type you've observed this with.
I'm likely to end up saying that manual umounting of automounted shares
is a bad thing and doing so may lead to unpredictable behavior. I may be
able to improve matters but it is unlikely to be totally reliable.
So I recommend leaving the automounts alone.
Ian
next prev parent reply other threads:[~2006-10-30 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 16:41 autofs 5 not recognizing manual umounts properly Timo Wendt
2006-10-30 6:35 ` Ian Kent [this message]
2006-10-30 9:53 ` Scott_Rochford
2006-10-30 10:49 ` Ian Kent
2006-10-30 9:19 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2006-10-31 19:46 twendt
2006-11-01 3:35 ` Ian Kent
2006-11-05 9:48 ` Ian Kent
2006-11-16 12:48 ` Timo Wendt
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=1162190102.2900.13.camel@localhost \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=twendt@online.de \
/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.