@barry - do you use lvm with schroot? I do and I am also affected by this bug.
$ schroot -e --all-sessions
E: 10mount: umount: /var/lib/schroot/mount/saucy-amd64-29694a5f-0def-40d4-9d3d-95bc27fa70f7: device is busy.
E: 10mount: (In some cases useful info about processes that use
E: 10mount: the device is found by lsof(8) or fuser(1))
E: saucy-amd64-29694a5f-0def-40d4-9d3d-95bc27fa70f7: Chroot setup failed: stage=setup-stop
@barry - do you use lvm with schroot? I do and I am also affected by this bug.
$ schroot -e --all-sessions schroot/ mount/saucy- amd64-29694a5f- 0def-40d4- 9d3d-95bc27fa70 f7: device is busy. 29694a5f- 0def-40d4- 9d3d-95bc27fa70 f7: Chroot setup failed: stage=setup-stop
E: 10mount: umount: /var/lib/
E: 10mount: (In some cases useful info about processes that use
E: 10mount: the device is found by lsof(8) or fuser(1))
E: saucy-amd64-
from /proc/mounts:
/dev/mapper/ virtual- -vg-saucy- -amd64- -29694a5f- -0def-- 40d4--9d3d- -95bc27fa70f7 /var/lib/ schroot/ mount/saucy- amd64-29694a5f- 0def-40d4- 9d3d-95bc27fa70 f7 ext4 rw,noatime, data=ordered 0 0
I wonder if this is related to bug 1223576 at all.