Comment # 7 on bug 1230010 from Fabian Vogt

(In reply to Fabian Vogt from comment #6)
> (In reply to Thorsten Kukuk from comment #5)
> > (In reply to Fabian Vogt from comment #4)
> > > The error message can be misleading: libmount shows the first mount of the
> > > source device if the mount syscall returns -EBUSY for whatever reason. In
> > > this case the most likely reason for that is that /.snapshots is already
> > > mounted.
> > > 
> > > Is this reproducible?
> > 
> > No, it's not. I saw this now during 3 days on two machines, all the other
> > machines and this ones rebooted without problems the other times.
> > 
> > > When the error happens, is /.snapshots already mounted? If not, what happens
> > > on systemctl start /.snapshots?
> > 
> > Forgot to check that. At least /.snapshots was mounted after I pressed
> > Ctrl-D and could login.
> 
> Ok, so the question is what mounts /.snapshots and why systemd didn't
> realize that before it attempted to start /.snapshots itself.

To find out what else mounts /.snapshots, I commented out the entry in
/etc/fstab and rebooted. The system booted successfully and /.snapshot was not
mounted, so I failed to reproduce the issue.