@Nigel - thanks, but near as I can tell all that was done on August 30.  Likely 
I goofed up and
missed some step.  Should I have placed *this* bug in FixReleased state?  (I 
thought that was
about the development release version, which is N/A here)

Thanks for any hints.

** Description changed:

  =========================== SRU request 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)
  
- TO REPRODUCE:  Install a system with a separate /var partition, and try to
+ 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.
  
  =============================  Original description
  =============================
  
  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://www.mail-archive.com/lxc-us...@lists.sourceforge.net/msg00032.html 
contains the patch for this problem.
  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

** Changed in: lxc (Ubuntu)
    Milestone: None => lucid-updates

-- 
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition - 
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to