We're seeing something very similar to this bug in 12.04LTS (kernel
3.2.0-49-generic) running LXC containers on overlayfs mounts. In our
case a front-end script we're using to run tests in isolation
successfully umounts the overlayfs after the contained test completes,
but attempting to rmdir the
This bug was fixed in the package linux - 3.9.0-5.12
---
linux (3.9.0-5.12) saucy; urgency=low
[ Andy Whitcroft ]
* Revert HAVE_CPLUS_DEMANGLE=n
* SAUCE: intel_pstate -- toggle default to disable
- LP: #1188647
* SAUCE: ubuntu: overlayfs -- ovl_path_open should not take
@serge -- after a lot of debugging I think we have this one nailed.
Could you test out the kernels for raring and saucy below and confirm
the resolve the umount issue:
http://people.canonical.com/~apw/lp1098378-raring/
http://people.canonical.com/~apw/lp1098378-saucy/
Please report your
Thanks Andy, that fixes it! (Tested the raring kernel).
I haven't explicitly tested in quantal, but suspect it was new in
raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098378
Title:
Indeed, quantal is not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098378
Title:
chroot+overlayfs seems to cause umount mis-behavior
To manage notifications about this bug go to:
both raring and saucy still do this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098378
Title:
chroot+overlayfs seems to cause umount mis-behavior
To manage notifications about this bug go to:
** Tags added: overlayfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098378
Title:
chroot+overlayfs seems to cause umount mis-behavior
To manage notifications about this bug go to:
Does this issue still exist in Raring with the latest updates? Also,
can you see if the bug also exists 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/1098378
Title:
chroot+overlayfs
** Tags added: kernel-stable-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098378
Title:
chroot+overlayfs seems to cause umount mis-behavior
To manage notifications about this bug go to:
Can you see if this also happens with the latest mainline kernel, which can be
downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc3-raring/
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for the automated comment ;) Overlayfs isn't a mainline feature
so we obviously can't test that kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098378
Title:
chroot+overlayfs seems to
** Tags added: needs-bisect raring
** Also affects: linux (Ubuntu Raring)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098378
Title:
chroot+overlayfs
** Attachment added: script to trigger the bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1098378/+attachment/3479756/+files/stgraber.script.5
** Description changed:
If you mount an overlayfs under a loopback fs, chroot into it and mount
something, then the loopback device
Marking confirmed as it's been seen by 1 people (stgraber and myself).
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
14 matches
Mail list logo
