Addition, that's what happens trying to close any of the open sessions: <cut>$ schroot -c session:sid-amd64-sbuild-d6d9a259-3c44-46b1-9814-8b404cac5c6b -e -f E: 15binfmt: update-binfmts: unable to open /var/lib/schroot/mount/sid-amd64-sbuild-d6d9a259-3c44-46b1-9814-8b404cac5c6b/bin/sh: No such file or directory E: 10mount: rmdir: failed to remove '/var/lib/schroot/mount/sid-amd64-sbuild-d6d9a259-3c44-46b1-9814-8b404cac5c6b': Device or resource busy E: sid-amd64-sbuild-d6d9a259-3c44-46b1-9814-8b404cac5c6b: Chroot setup failed: stage=setup-stop
</cut> Daniel Stender On 31.08.2014 15:04, Daniel Stender wrote:
Hi, after some sbuild breaks which came from experimenting with setting up ccache with sbuild (https://wiki.debian.org/sbuild) I've now discovered that there are several schroot sessions permanently running at the same time on my system, which I can't close because it says "resource busy". To make it clearer, this is what my mount looks like: http://paste.debian.net/118558/ I need schroot exprienced help to recover a clean system. Greetings, Daniel Stender
-- http://www.danielstender.com/blog PGP key: 2048R/1DFED696