[Pkg-systemd-maintainers] Bug#721775: systemd: can't umount schroot after reboot

[Michael Biebl]

Am 04.09.2013 01:45, schrieb Brian May:
> aquitard# umount /var/lib/schroot/union/underlay/squeeze-f8ea98e7-1bac-43d1-b774-94c9c42fddc7
> umount: /var/lib/schroot/union/underlay/squeeze-f8ea98e7-1bac-43d1-b774-94c9c42fddc7: device is busy.
>         (In some cases useful info about processes that use
>          the device is found by lsof(8) or fuser(1))
> 
> aquitard# fuser -vm /var/lib/schroot/union/underlay/squeeze-f8ea98e7-1bac-43d1-b774-94c9c42fddc7
>                      USER        PID ACCESS COMMAND
> /var/lib/schroot/union/underlay/squeeze-f8ea98e7-1bac-43d1-b774-94c9c42fddc7:
>                      root     kernel mount /var/lib/schroot/union/underlay/squeeze-f8ea98e7-1bac-43d1-b774-94c9c42fddc7

So I assume after the reboot it is the schroot init script which mounts
that file system or is that mount point in /etc/fstab?
systemd only mounts a few internal API file systems and what it finds in
/etc/fstab.

But if I read you correctly, the above means, that there is a running
mount process which was spawned to mount that lvm volume and that mount
process did not exit?
And this behaviour you only get with systemd?



Michael





-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20130904/73753064/attachment-0002.sig>