Displaying 5 results from an estimated 5 matches for "8ptb".
Did you mean:
8pt
2016 Apr 26
2
Re: /proc/meminfo
...ut
> Alloc 100 Mb
> Alloc 200 Mb
> Alloc 300 Mb
> Alloc 400 Mb
> Alloc 500 Mb
> Alloc 600 Mb
> Alloc 700 Mb
> Alloc 800 Mb
> Alloc 900 Mb
> Alloc 1000 Mb
> Killed
>
> Broken only fuse mount. It's positive news - process inside container
> even in case 8Ptb can't allocate more memory that set in cgroups.
> But negative news - that some java based sotfware (as puppetdb in our
> case) plan self strategy based on 8Ptb memory and collapsed after
> reach real limit.
>
> resume:
> 1) don't start disabled service by systemd
>...
2016 Apr 26
1
Re: /proc/meminfo
...--without uml \
> --without vbox \
> --without selinux \
> --with lxc \
> --with macvtap \
> --without storage-rbd \
> --with capng
>
> Kernel 3.10.0-327.13.1.el7.x86_64
> With version 1.2.18 we had 2 problem - negative value in "used" column
> and 8Ptb in "total" column.
> In 1.3.2 "used" columns always show positive values.
>
> b.r.
> Maxim Kozin
>
Thanks, can you file a bug report about the 'total' issue, and paste in the
steps to reproduce. Just so it doesn't get lost on the mailing list
http...
2016 Apr 26
0
Re: /proc/meminfo
...9
Swap: 0 0 0
[root@tst-mxs2 ~]# ./a.out
Alloc 100 Mb
Alloc 200 Mb
Alloc 300 Mb
Alloc 400 Mb
Alloc 500 Mb
Alloc 600 Mb
Alloc 700 Mb
Alloc 800 Mb
Alloc 900 Mb
Alloc 1000 Mb
Killed
Broken only fuse mount. It's positive news - process inside container
even in case 8Ptb can't allocate more memory that set in cgroups.
But negative news - that some java based sotfware (as puppetdb in our
case) plan self strategy based on 8Ptb memory and collapsed after
reach real limit.
resume:
1) don't start disabled service by systemd
2) workaround by cglassify or by i...
2016 Mar 23
7
/proc/meminfo
Has anyone seen this issue? We're running containers under CentOS 7.2
and some of these containers are reporting incorrect memory allocation
in /proc/meminfo. The output below comes from a system with 32G of
memory and 84GB of swap. The values reported are completely wrong.
# cat /proc/meminfo
MemTotal: 9007199254740991 kB
MemFree: 9007199224543267 kB
MemAvailable: 12985680
2016 Apr 26
0
Re: /proc/meminfo
...esx \
--without parallels \
--without bhyve \
--without uml \
--without vbox \
--without selinux \
--with lxc \
--with macvtap \
--without storage-rbd \
--with capng
Kernel 3.10.0-327.13.1.el7.x86_64
With version 1.2.18 we had 2 problem - negative value in "used" column
and 8Ptb in "total" column.
In 1.3.2 "used" columns always show positive values.
b.r.
Maxim Kozin