[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition - container does not start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Lucid |
Invalid
|
Medium
|
Serge Hallyn |
Bug Description
=======
IMPACT: users with separate /var partition cannot start containers
HOW ADDRESSED: the fix was applied upstream some time ago, and is
rolled into the maverick package. The proposed package attached to this
bug cherrypicks the specific patch.
PATCH: a debdiff is attached below (comment #23)
TEST CASE: Install a system with a separate /var partition, and try to
start a container.
REGRESSION POTENTIAL: The patch is only to lxc code, so no non-lxc
code should be affected. As for lxc itself, this simply makes it do
'umount -l' instead of 'umount', so lxc should not regress either.
=======
Binary package hint: lxc
I have /var on a separate partition.
As described in lxc-users, this prevents containers from startup:
$ lxc-start --name lemon -l DEBUG -o $(tty)
...
lxc-start [timestamp] ERROR lxc_conf - Device or resource busy - could not unmount old rootfs
The post http://<email address hidden>
This patch is already included in git.
Attaching this patch here since the error message does not really have any clue about what to do.
Installed: 0.6.5-1
Linux fridge 2.6.32-21-server #32-Ubuntu SMP Fri Apr 16 09:17:34 UTC 2010 x86_64 GNU/Linux
Related branches
- Mathias Gug: Needs Fixing
-
Diff: 158 lines (+111/-3)5 files modifieddebian/changelog (+8/-0)
debian/control (+2/-1)
debian/patches/00list (+1/-0)
debian/patches/use-mnt-detach.patch.dpatch (+89/-0)
debian/rules (+11/-2)
description: | updated |
description: | updated |
Changed in lxc (Ubuntu): | |
milestone: | none → lucid-updates |
I have packaged the fix for 0.6.5-1 in ppa:~rye/ppa: 0.6.5-1ubuntu1~ ppa1~lucid