Hi all,
We encounter a bug today when one of our systems enter soft-lockup when we try
to start a container. Unfortunately at that point, we have to do a power cycle
because we can’t access the system anymore. Here is the kernel.log:
[14164995.081770] BUG: soft lockup - CPU#3 stuck for 22s!
Hi,
We run a ( sort of ) unconventional FS layout with aufs.
bind-mountaufs
/var/lib/lxc/container --- /disk1/container++ base
|
++
So does the same thing happen if you don't have the
/var/lib/lxc/container bind mount, and instead do
lxc-start -P /desk1 -n container
?
does 'grep shared /proc/self/mountinfo' show anything?
Quoting Dao Quang Minh (dqmin...@gmail.com):
Hi,
We run a ( sort of ) unconventional FS layout
We havent tested without the bind mounts ( but we can probably try it asap
). We migrated to 1.0.0 from 0.7.5 about a week ago, and this is the first
time i've seen this bug.
`grep shared /proc/self/mountinfo` doesnt show anything, but
`/proc/self/mountinfo` does display 2 entries per physical
Quoting Dao Quang Minh (dqmin...@gmail.com):
We built the kernel based on ubuntu tree with some patches backported from
3.14 ( https://github.com/nitrous-io/linux/commits/stable-trusty )
I can try to run another stress test to see if we can replicate the bug
with the debug kernel.
Hmm,
Is there an environmental variable or command line option to select a custom
directory for lxc-… template files? I’d like to make changes to the default for
my distribution, but do not want these changes overwritten with a new version.
Is this possible?
Thanks!
Sarah
Quoting Sarah Collison (sa...@clingclangclick.com):
Is there an environmental variable or command line option to select a custom
directory for lxc-… template files? I’d like to make changes to the default
for my distribution, but do not want these changes overwritten with a new
version. Is
On 03/04/2014 12:04 AM, Serge Hallyn wrote:
No - I take it you can still reproduce? What might be helpful is if you
could show how to start from a fresh ec2 or rackspace cloud instance
(specifying which AMI or distro/release to start from), and show the
precise commands you are using to
On 03/12/2014 11:17 PM, Serge Hallyn wrote:
Quoting Tamas Papp (tom...@martos.bme.hu):
On 03/04/2014 12:04 AM, Serge Hallyn wrote:
No - I take it you can still reproduce? What might be helpful is if you
could show how to start from a fresh ec2 or rackspace cloud instance
(specifying which
