search for: 84gb

Displaying 9 results from an estimated 9 matches for "84gb".

Did you mean: 4gb
2016 Mar 23
2
Re: /proc/meminfo
...03/23/2016 12:10 PM, Peter Steele wrote: >> 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. >> > There was a meminfo bug here: > > https://bugzilla.redhat.com/show_bug.cgi?id=1300781 > > The initial report is fixed in git, however the reporter also mentioned the > issue you are seeing. I suspect something is going...
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 kB Buffers: 0 kB Cached: 119744 kB SwapCached: 10804 kB Active: 110228 kB Inactive:...
2016 Mar 23
0
Re: /proc/meminfo
On 03/23/2016 12:10 PM, Peter Steele wrote: > 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. > There was a meminfo bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1300781 The initial report is fixed in git, however the reporter also mentioned the issue you are seeing. I suspect something is going wacky with the memory values w...
2016 Mar 23
0
Re: /proc/meminfo
...PM, Peter Steele wrote: >>> 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. >>> >> There was a meminfo bug here: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1300781 >> >> The initial report is fixed in git, however the reporter also mentioned the >> issue you are seeing. I...
2016 Mar 24
0
Re: /proc/meminfo
Hi all > 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. yes, it's occured time to time on our installations. Centos 7.2 + libvirt 1.2.18 and probably on 1.3.2 We have workaround for fix it without reboot LXC container. 1) check that on HW node exists cgroups memory for container. [root@node]# cat /s...
2016 Apr 26
0
Re: /proc/meminfo
...3/23/16, Peter Steele <pwsteele@gmail.com> wrote: > 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 kB > Buffers: 0 kB > Cached: 119744 kB > SwapCached: 10804 kB >...
2010 Mar 23
1
[RFC] vhost-blk implementation
...e done simple tests to see how it performs. I got very encouraging results on sequential read tests. But on sequential write tests, I see degrade over virtio-blk. I can't figure out and explain why. Can some one shed light on whats happening here ? Read Results: ============= Test does read of 84GB file from the host (through virtio). I unmount and mount the filesystem on the host to make sure there is nothing in the page cache.. with vhost-blk: ---------------- # time dd if=/dev/vda of=/dev/null bs=128k iflag=direct 640000+0 records in 640000+0 records out 83886080000 bytes (84 GB) copied...
2010 Mar 23
1
[RFC] vhost-blk implementation
...e done simple tests to see how it performs. I got very encouraging results on sequential read tests. But on sequential write tests, I see degrade over virtio-blk. I can't figure out and explain why. Can some one shed light on whats happening here ? Read Results: ============= Test does read of 84GB file from the host (through virtio). I unmount and mount the filesystem on the host to make sure there is nothing in the page cache.. with vhost-blk: ---------------- # time dd if=/dev/vda of=/dev/null bs=128k iflag=direct 640000+0 records in 640000+0 records out 83886080000 bytes (84 GB) copied...
2007 Aug 07
4
Will this work? server+centOS5+100users?
I am an experienced MS administrator of W2003 servers & Exchange systems. I have 5+ years UNIX mid-level experience but not in centOS. Grounded in SCO UNIX (the real SCO UNIX). We want to use CentOS on a recently grave yarded Dell poweredge 400SC server. This is a P4 3.0 Ghz, w/4GB memory, 2 SATA 250 GB disks. We want to use this server w/CentOS5, to provide file and print resources to 100