[buildd-tools-devel] Bug#681884: Bug#681884: schroot: Does not always clean up after itself.

[Kurt Roeckx]

On Tue, Jul 17, 2012 at 04:58:14PM +0100, Roger Leigh wrote:
> On Tue, Jul 17, 2012 at 03:41:05PM +0200, Kurt Roeckx wrote:
> > I've set up a schroot of type=directory and pointed directory to
> > the right place, but when I then call schroot to get into that,
> > and then left it, it reguarly fails with:
> > E: 10mount: umount: /var/lib/schroot/mount/i386-sid-8850e601-cd43-4a82-b87c-08a8120619bd/home: 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: i386-sid-8850e601-cd43-4a82-b87c-08a8120619bd: Chroot setup failed: stage=setup-stop
> 
> What type of filesystem is /home?

/home is on / and / is ext4.

> Is there anything running on your system (outside the chroot) which
> has files/directories open inside the chroot?

Of course I have things running outside the chroot that have files
open in /home.

But there is nothing that does anything with /var/lib/schroot

> Is there anything
> inside which is running despite the 15killproc script having been
> run?

Their shouldn't.  The only thing I started in the schroot was bash and ls,
no reason for anything to be running there that I started.

It's reproducible, but I now need to try like 20 times.

> Does lsof report any processes with open file descriptors in the
> chroot?  (Could also be the process cwd.)

No.


Kurt