CT memory maxed out

Henry

Member
Jan 1, 2016
83
0
6
51
I have a CT with 512mb ram and after boot it only uses 128mb or so.

When I copy a large amount of data to the CT the memory maxes out at 512mb

After the copy has completed the memory in use remains at 512mb

If I reboot the CT the memory in use returns to 128mb
 
what is the problem?
 
actually, just checking there is not a problem. is this behaviour normal/expected ?

why does the memory usage increase to 512mb and after completion of the job I would have expected the memory usage to return to 128mb...
 
Hi Dietmar, I was monitoring the memory usage using the Proxmox GUI, CT summary tab.

The source and destination were Samba shares that I copied between using my Ubuntu desktop PC.
 
I am a VERY new user so I would expect i am using the newest versions of everything.

How can I verify this?
 
What is the output of:

# pveversion -v

You can update with

# apt-get update
# apt-get dist-upgrade
 
root@pve:~# pveversion -v
proxmox-ve: 4.1-28 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-2 (running version: 4.1-2/78c5f4a2)
pve-kernel-4.2.6-1-pve: 4.2.6-28
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-29
qemu-server: 4.0-42
pve-firmware: 1.1-7
libpve-common-perl: 4.0-42
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-18
pve-container: 1.0-35
pve-firewall: 2.0-14
pve-ha-manager: 1.0-16
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie
 
looks OK. And you still get that behavior? I am unable to reproduce it here.

Note: I you updated recently, It may help if you stop the container, then start it again.