Control: tag -1 = confirmed upstream patch
[Answering to a relatively old bugreport, so not removing context...]
On 25.06.2012 14:02, Marc Lehmann wrote:
> On Sun, Jun 24, 2012 at 10:23:24PM +0300, Michael Tokarev <m...@tls.msk.ru>
> wrote:
>>> seems the symlink mount has also been removed - I have since switched to
>>> am-utils, which solves both problems, as autofs seems to be eternally
>>> broken.
>>
>> Can you please show the options or maps you were using with autofs?
>
> /etc/auto.master
>
> /fs /etc/maps/fs nobind
>
> /etc/maps/fs
>
> doom_db -symlink :/db
>
> That's a symlink mount - it simply creates a symlink (it can also be used
> with an nfs mount and will symlink instead of bind for normal mounts,
> thus my confusion with nobind, which I believed to do the same).
Ok. I finally was able to reproduce this (it turned out to be not so easy :).
And even more, apparently upstream has a fix now:
commit ebc62059641517ea4d219fa1ecc17b92acef6cc0
Author: Ian Kent <ik...@redhat.com>
Date: Wed Sep 12 09:09:49 2012 +0800
autofs-5.0.7 - fix nobind sun escaped map entries
If a map contains a Sun colon escape to indicate the mount is a local
file system and the "nobind" option is present there is no hostname in
the mount location and the mount fails.
But note: -symlink option does not exist. There's "nosymlink" option,
but it is not used anymore, it is left for compatibility -- at least
as stated in comments in the code, however it actually IS used down
the line, to mean exactly the same as "nobind". So your confusion
is not without a reason.
>> Yes, apparently autofs (both user and kernel space) has quite some
>> bugs, but maybe it's a good idea to fix at least some of them...
>
> Right, but despite many people reporting them repeatedly, they have not
> been fixed for half a decade, so I decided it's pointless to hope for
> fixes - they are not coming to be, and upstream sometimes outright refuses
> to fix bugs (race condition on recursive mounts, see e.g. 556910). That's
> definitely not a debian problem, previous maintainers have reported bugs
> (sometimes with patches) to upstream, it's just that upstream isn't
> responsive, and bugs keep coming back.
>
> (As far as I know, the -symlink mount option was added by a previous
> debian maintainer because upstream refused to fix the underlying problem,
> and smylinks work around it nicely).
Aha. I didn't know that. This is actually rather bad, maybe we should
add a compatibility option too, -- because right now, when I specify
-nosymlink, it is passed to mount.nfs, and the result is, well, wrong
ofcourse. I'll dig into that.
> The tragedy is that I so wanted to get away from amd, the menace of
> the early 90ies, but to my surprise, amd is much more stable, and even
> restarts cleanly, something I could never pull off with automount, wow,
> why didn't I switch back earlier :) I don't even need to touch every
> single mount point manually anymore after starting automount to avoid
> races!
>
> As far as I can see, the only drawback of am-utils over automount is that
> the former uses 5mb rss, and the latter 2mb. If not for that, there would
> be absolutly no reason to keep automount.
>
> So, from a purely technical perspective, the best way to fix autofs is
> to get rid of it, as am-utils now supports sun-style automount maps and
> the autofs filesystem. Ghosting doesn't work with amd and the autofs
> filesystem, but that never worked reliably with automount either.
Oh well. But heck, we can't do that for wheezy at least :)
Now, having said all that, maybe it is a stupid idea to ask you for some
testing/comments on the new package I created, preliminary version of
stuff I want to upload, located at http://www.corpit.ru/mjt/tmp/autofs/ ?
Anyway, the bug you reported appears to be fixed now.
Thank you for your patience (or lack thereof)! :)
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
