Hi Christian,
On 12/11/17 4:17 PM, Christian Brauner wrote:
What is the container's config file? liblxc itself does not know what
drbd devices are and cannot create such containers. So I expect your
container's config file to contain a line like:
lxc.rootfs = /data1//rootfs
Here is a sample
Hi Serge,
On 12/11/17 4:40 AM, Serge E. Hallyn wrote:
Quoting Harald Dunkel (ha...@afaics.de):
On 12/07/17 22:30, Serge E. Hallyn wrote:
What filesystem are you using?
ext4 on a drbd block device:
/dev/drbd1 /data1 ext4 rw,noatime,stripe=256,data=ordered 0 0
I have to think drbd would be
On Sun, Dec 10, 2017 at 12:59:23PM +0100, Harald Dunkel wrote:
> On 12/07/17 22:30, Serge E. Hallyn wrote:
> >
> > What filesystem are you using?
>
> ext4 on a drbd block device:
>
> /dev/drbd1 /data1 ext4 rw,noatime,stripe=256,data=ordered 0 0
What is the container's config file? liblxc itself
Quoting Harald Dunkel (ha...@afaics.de):
> On 12/07/17 22:30, Serge E. Hallyn wrote:
> >
> > What filesystem are you using?
>
> ext4 on a drbd block device:
>
> /dev/drbd1 /data1 ext4 rw,noatime,stripe=256,data=ordered 0 0
I have to think drbd would be the problem. But I assume you
haven't see
On 12/07/17 22:30, Serge E. Hallyn wrote:
>
> What filesystem are you using?
ext4 on a drbd block device:
/dev/drbd1 /data1 ext4 rw,noatime,stripe=256,data=ordered 0 0
Regards
Harri
signature.asc
Description: OpenPGP digital signature
___
lxc-deve
Quoting Harald Dunkel (harald.dun...@aixigo.de):
> Hi folks,
>
> If a LXC server ran for several weeks and if I try to stop a
> container, then the server gets stuck for a few minutes (see
> attachment).
>
> Please note the
>
> :
> [8541088.226013] Task dump for CPU 31:
> [8541088.226015] mount
Hi folks,
If a LXC server ran for several weeks and if I try to stop a
container, then the server gets stuck for a few minutes (see
attachment).
Please note the
:
[8541088.226013] Task dump for CPU 31:
[8541088.226015] mount R
:
This might be common for all incidents of this kind, bu
