On Mon, Sep 29, 2014 at 04:30:31PM -0700, Eric W. Biederman wrote: > Ross Lagerwall <rosslagerwall@xxxxxxxxx> writes: > > I hope someone has an idea of what's going on or how to debug this > > because I've run out of ideas... > > My guess is that some process (systemd?) is configured to unmount that > directory if anything shows up mounted on it. So when the mount > propogates it gets unmounted and then the unmount propogates as well. > Ah yes! I'd forgotten that I previously had experimented with a mount unit file for that directory and didn't realize that systemd would actively prevent anything from being mounted at that point even if the mount unit was inactive. Turning up systemd's log level showed the following: Sep 30 06:59:28 hobo systemd[279]: mnt-puppy.mount changed dead -> mounted Sep 30 06:59:28 hobo systemd[1]: mnt-puppy.mount changed dead -> mounted Sep 30 06:59:28 hobo systemd[1]: Unit mnt-puppy.mount is bound to inactive service. Stopping, too. Sep 30 06:59:28 hobo systemd[1]: Trying to enqueue job mnt-puppy.mount/stop/fail Sep 30 06:59:28 hobo systemd[1]: Installed new job mnt-puppy.mount/stop as 240 Sep 30 06:59:28 hobo systemd[1]: Enqueued job mnt-puppy.mount/stop as 240 Sep 30 06:59:28 hobo systemd[1]: Unmounting /mnt/puppy... Sep 30 06:59:28 hobo systemd[1]: About to execute: /bin/umount -n /mnt/puppy Thanks for pointing me in the right direction! -- Ross Lagerwall -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
