** Changed in: sbuild (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10mount: umount: /<>/dev: device is busy
To manage notifications about
I meant is now fixed in Saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10mount: umount: /<>/dev: device is busy
To manage notifications about this bug go to:
https://bugs.launch
Bug 1223576 is not fixed in Saucy and I have not encountered this issue
again, however I have not built a lot of packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10mount: umount
** Changed in: sbuild (Ubuntu)
Importance: Undecided => High
** Changed in: schroot (Ubuntu)
Importance: Undecided => High
** Changed in: sbuild (Ubuntu)
Status: Confirmed => Triaged
** Changed in: schroot (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notif
Brian Murray:
> I wonder if this is related to bug 1223576 at all.
I would highly suspect so; schroot has been plagued with lvremove
failures for some time, and this looks like a likely candidate for why
lvremove was failing--all the symptoms are suspiciously similar. If so,
I'll be very happy--n
@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:
On Sep 12, 2013, at 05:30 PM, Brian Murray wrote:
>@barry - do you use lvm with schroot?
I actually don't, but I do sometimes see error messages like this. Nothing
actually bad happens afaict. A reboot then `schroot -e --all-sessions`
usually clears things up.
--
You received this bug notific
** Changed in: sbuild (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10mount: umount: /<>/dev: device is busy
To manage notifications about this
** Bug watch added: Debian Bug tracker #681884
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681884
** Also affects: sbuild (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681884
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
possibly related to debian bug #681884 schroot: Does not always clean up after
itself
repro'd this gaming in a schroot with mounts that opened in both chroot
namespaces causing failure to tidily exit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I'm on 12.04
in my case I'm seeing libvirtd continuesly respawning and mounting the device
some how.
umount /var/lib/schroot/mount/precise-2d97fb31-1cae-47e4-a363-0a652a518610/dev
root@bork:~# lsof | grep
/var/lib/schroot/mount/precise-2d97fb31-1cae-47e4-a363-0a652a518610/dev
dbus-daem 19780
on another ubuntu machine (oneiric server) i get leftover mounts like:
proc on
/var/lib/schroot/mount/bootstrap-administrator-1b79165b-24ab-4a6d-8460-4f1ca45927d8/proc
type proc (rw)
/dev/pts on
/var/lib/schroot/mount/bootstrap-administrator-1b79165b-24ab-4a6d-8460-4f1ca45927d8/dev/pts
type non
output of cat /proc/mounts
** Attachment added: "proc-mounts.txt"
https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/917339/+attachment/3168709/+files/proc-mounts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
output of lsof
** Attachment added: "lsof.txt"
https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/917339/+attachment/3168710/+files/lsof.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
This bug report does not mention exactly what the device is which
couldn't be umounted. Note that if we can't umount, we don't end the
session, or else we could end up leaking resources e.g. LVM snapshots,
which would also be quite annoying.
Please could you provide: the result of 'cat /proc/moun
Also, as the message stated, the output of 'lsof' would also be helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10mount: umount: /<>/dev: device is busy
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: schroot (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10m
** Also affects: schroot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10mount: umount: /<>/dev: device is busy
To manage notifica
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sbuild (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10mo
19 matches
Mail list logo