On Thu, 2012-07-26 at 08:35 +0200, jbd@xxxxxxxxxxx wrote: > On Thu, 26 Jul 2012 11:08:59 +0800, Ian Kent <raven@xxxxxxxxxx> wrote: > > When the mount is busy on re-load the automount stored cached map entry > > must be left in place so that in can be expired. That's what causes it. > > When you say that the "stored cached map entry must be left in place", > you mean in the > direct map file or the automount internal state ? Internal state. autofs uses a stored copy of map info quite a lot. > > If I re-load the automount (after removing the corresponding line in > the map) while the mount is busy > and move away from this mount, the timeout expires and the unmount > occurs although it is not here anymore > in the map file. > > Sorry, I didn't really get your answer :/ > > > Not really wanted behavior but it is what happens now. > > I should be able to mark the cached map entry negative on re-load so it > > doesn't trigger a mount while waiting to be cleaned up. > > What do you mean by "waiting to be cleaned up" ? To be unmounted or > this is pure > internal stuff ? In my test (reloading the map while having a busy > mount), after the timeout, > the unmount happens (that's what I understand as "to be cleaned up"), > but I can still mount it after. > > Sorry to repeat myself, but I just want to be sure we're talking about > the same behaviour. > > > The --ghost has no meaning for direct mounts, it isn't needed. > > Indeed ! > > Thank you for your answer ! > > Jean-Baptiste > -- To unsubscribe from this list: send the line "unsubscribe autofs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
