If this is an upstream issue, I think it's best to be handled by for someone more familiar with reporting issues on the kernel mailing list. But I am not sure if it's not due to the specific set of patches applied by Gentoo. autofs 5.0.3-r6 doesn't have the bug, but 5.0.4-r5 and ~5.0.5 do. In auto.master, put /mnt/test /etc/auto.test --ghost In auto.test, put floppy -fstype=auto :/dev/fd0 (or anything else, really) Start autofs, observe /mnt/test/floppy, send SIGHUP to automount (/etc/init.d/autofs reload) - /mnt/test/floppy is not gone. This is problematic when auto.test is maintained via udev (autofs needs to be restarted after disks are disconnected).
> send SIGHUP to automount (/etc/init.d/autofs reload) Sorry, meant - send SIGHUP after commenting out the line in auto.test.
(In reply to comment #1) > > send SIGHUP to automount (/etc/init.d/autofs reload) > > Sorry, meant - send SIGHUP after commenting out the line in auto.test. This kind of confuses me... Do you start up autofs and then comment out the entry in auto.test and after restarting autofs (either by /etc/init.d/autofs restart or sending SIGHUP) the entry in /mnt/test is gone? Could you please clarify this and give a clear set of instruction how to reproduce this? At the moment, I think this not as a bug. But this might be due my confusion...
> Do you start up autofs and then comment out the entry in auto.test and after restarting autofs (either by /etc/init.d/autofs restart or sending SIGHUP) the entry in /mnt/test is gone? The entry in /mnt/test should be gone after SIGHUP, but it is not gone in autofs >= 5.0.4. > Could you please clarify this and give a clear set of instruction how to reproduce this? Sure, the steps are: 1. put "/mnt/test /etc/auto.test --ghost" in auto.master 2. put "floppy -fstype=auto :/dev/fd0" in auto.test 3. start autofs (/etc/init.d/autofs start) 4. see that /mnt/test/floppy exists 5. comment out the line in auto.test 6. send SIGHUP to autofs (/etc/init.d/autofs reload) 7. see that /mnt/test/floppy *still* exists (it shouldn't, as far as I understand) Think about implementing automatic creation and removal of ghost mount points on top of udev. With autofs >= 5.0.4, you have to do a full "/etc/init.d/autofs restart" at step 6, which is ugly and error-prone. Thanks!
Hi, any news? Is it indeed a bug in autofs?
Apparently, a fix for 5.0.5 will be added to the patchset: http://linux.kernel.org/pipermail/autofs/2011-January/006324.html
(In reply to comment #5) > Apparently, a fix for 5.0.5 will be added to the patchset: > http://linux.kernel.org/pipermail/autofs/2011-January/006324.html Thanks. I added this patch to the rev bumped ebuild which hopefully will be in tree soon (see bug #346537). You can use that ebuild in your local overlay until it hits the tree. BR, Dustin
Fixed in 5.0.5-r1.
