Thank you! With 'cp' the job was killed. There was error message:
Mar 10 09:50:04 kernel: SLUB: Unable to allocate memory on node -1
(gfp=0x8020)
Mar 10 09:50:04 kernel: cache: kmalloc-64(5:step_0), object size: 64,
buffer size: 64, default order: 0, min order: 0
Mar 10 09:50:04 kernel: node 0
On Mar 10, 2017, at 3:51 PM, Wensheng Deng wrote:
>
> I have 3.10 kernel. I am running some data processing job, need to first
> copy big (>5 GB) input files. The jobs were killed, because the system
> thought I used 5 GB memory from the file copying.
If you’re using ‘cp’ you probably aren’t usi
Well, that is exactly what it is supposed to do. The easy way to fix
this is add more memory. A wildly impractical attempt to turn off memory
accounting will result in a really borked system that will suck up all
your time trying to recompile the kernel to make it work. Don't even go
down that
I have 3.10 kernel. I am running some data processing job, need to first
copy big (>5 GB) input files. The jobs were killed, because the system
thought I used 5 GB memory from the file copying.
On Fri, Mar 10, 2017 at 3:04 PM, David Both wrote:
> First - why in the world would you want to disab
First - why in the world would you want to disable kernel memory
accounting? I don't think that is even possible (despite not being a
kernel programmer myself) because the kernel must needs account for
every bit of real and virtual memory in the system in order to do its job.
Second - the firs
Hi CentOS experts,
I am using CentOS 7. Trying to disable kernel memory accounting:
according to https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt,
passing cgroup.memory=nokmem to the kernel at boot time, should be able to
archive that.
However it is not the case in my exercise. The
6 matches
Mail list logo
