I only started using lxc+btrfs in the past few months, so unfortunately
I have no information about the behavior of any previous kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1214
Additional note: I've found the problem manifests more easily with the
following modified test script (this one forks all LXC clone/start
operations immediately):
test.sh:
#!/usr/bin/env bash
prefix=$1
test -z "${prefix}" && echo 'error: missing required parameter: prefix'
Joseph Salisbury: I installed v3.11 RC2 and successfully reproduced the
problem using the same technique. The result remains the same - after a
series of simultaneous clone/start operations, LXC eventually fails to
be able to start any additional containers.
** Changed in: linux (Ubuntu)
S
Brad Figg: I'm happy to do this, but this is a server without a GUI, and
the spawned w3m instance is unable to properly display the login form
page.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
Using lxc with a btrfs filesystem can lead to system corruption and
containers which are unable to boot when many containers are created and
started simultaneously.
Packages involved:
- btrfs-tools
- ubuntu-lxc/daily from http://ppa.launchpad.net/ubuntu-lxc/daily/ubu
5 matches
Mail list logo
