From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 17C1C690B2 for ; Tue, 22 Mar 2022 16:03:19 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0D7771F24A for ; Tue, 22 Mar 2022 16:02:49 +0100 (CET) Received: from mx0.matrixscience.co.uk (mx0.matrixscience.co.uk [83.217.111.202]) by firstgate.proxmox.com (Proxmox) with ESMTP id 984EC1F23F for ; Tue, 22 Mar 2022 16:02:48 +0100 (CET) Received: from [127.0.0.1] (sshgate.matrixscience.co.uk [192.168.8.120]) by mx0.matrixscience.co.uk (Postfix) with ESMTPS id 9E8E22C03DC for ; Tue, 22 Mar 2022 14:56:29 +0000 (GMT) Message-ID: <012c61c6-6e2b-7da0-7044-efaeafedbea6@matrixscience.com> Date: Tue, 22 Mar 2022 14:56:28 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Content-Language: en-US To: PVE User List From: Adam Weremczuk Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.502 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [PVE-User] swap maxed out when plenty of RAM available X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2022 15:03:19 -0000 Hi all, I run a tiny and lightweight Debian 9.9 LXC container on Proxmox 6.2-6. It has 512 MB of memory and 512 MB of swap assigned and typically needs 50-100 MB to operate. Last year I started seeing about half of swap being used with very little use of RAM. I then made the following changes: /etc/sysctl.d/60-my-swappiness.conf vm.swappiness=10 /etc/sysctl.conf vm.swappiness=10 and rebooted. The container was running like that for several months until this morning when its core service (dhcp) started failing. I logged in to investigate and noticed 100% of swap being used with maybe 10-20% of RAM in use. Before I had time to look into details the container crashed (powered off). I'll probably try to get rid of swap entirely as an experiment to see what happens. Unless somebody has any better ideas and hints? Regards, Adam