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 9E512924DE for ; Wed, 28 Dec 2022 12:45:18 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7E174244E0 for ; Wed, 28 Dec 2022 12:45:18 +0100 (CET) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 28 Dec 2022 12:45:17 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 0369E3200926; Wed, 28 Dec 2022 06:45:15 -0500 (EST) Received: from imap50 ([10.202.2.100]) by compute5.internal (MEProxy); Wed, 28 Dec 2022 06:45:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dearriba.es; h= cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1672227915; x=1672314315; bh=l1Onmy5zbi lM8LRS7Vt4OyAJlnozltN00c+7c0W59s4=; b=boT/WpA+lRIN6lDVxOfbUbc6bw ApI62wdX51psApPnuhcXOfcTuE8r44TS34o3SPnMVQNL7hJm1ypMMehXfieevIVV +A9i56zYs6obcbzN8KFcKb7tr/PEB6R9VutHBt7nDq7T1ZsWn/rWhF7qfGkR2ur2 n1mz/sURJp7os3zwM7l6M7PmSONCyhlsUC04ezWXwjETIN6aL+O8CAv7ltmlJYUh mzBk730Uv1CZ44Wo9Ep2+IIh7SZzq3TLaUccP1Pg08AnN0LBmyz8EVTAcEBSof9H Gownjs5gAVOsHFkNjP7vUveY8voYeYLvnQXlGa/bKuc6/uRF03pu5pbzW1hQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1672227915; x=1672314315; bh=l1Onmy5zbilM8LRS7Vt4OyAJlnoz ltN00c+7c0W59s4=; b=g5bYnkxT4uXYBPqKkqqzxhiM2Hwa+RkfKxHxElqiRwO5 kfULfekfvYsRTdkJ5yOOOavNtK70ZERHFTdJl92JPKzJggUlPRHtAlcKI3AmlAdB Ky8fm4ZsLV3HWgnXIuvR/xdQ17OEsVgrzcIo6/v7sxs/GXCco4UQhZhIECqZxlxe 1SELloUPJJVrBfggi7VDihpMxs626SLnGvaE4+1C9PNjiNtm3iZRrfm6ZGF6TUfu zDu1y0yQIqPPewwJpUR9W35r1tGSL4GZG+OhZyy4qljP+c7L8TSI7kjsRrwUF7CT XafOuU9jdPToO9++MX9Y5fm7oIbDx9DxO24VOrLk3w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedriedvgdefvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepmnhstggrrhcuuggvucetrhhrihgsrgcuoehoshgtrghrsegu vggrrhhrihgsrgdrvghsqeenucggtffrrghtthgvrhhnpeehtdetueekfefhueekleeife etgeefkeekhfekkefgieejleekhedtjeeludeukeenucevlhhushhtvghrufhiiigvpedt necurfgrrhgrmhepmhgrihhlfhhrohhmpehoshgtrghrseguvggrrhhrihgsrgdrvghs X-ME-Proxy: Feedback-ID: ib1694623:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 34BAE1700089; Wed, 28 Dec 2022 06:45:15 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-1185-g841157300a-fm-20221208.002-g84115730 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Wed, 28 Dec 2022 12:44:54 +0100 From: =?UTF-8?Q?=C3=93scar_de_Arriba?= To: pve-user@lists.proxmox.com, martin@holub.co.at X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain HTML_MESSAGE 0.001 HTML included in message JMQ_SPF_NEUTRAL 0.5 SPF set to ?all RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust RCVD_IN_MSPIKE_H2 -0.001 Average reputation (+2) SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] Thin LVM showing more used space than expected 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: Wed, 28 Dec 2022 11:45:18 -0000 Hi Martin, > Did you try to run a fstrim on the VMs to regain the allocated space? At least on linux something like "fstrim -av" should do the trick. I did it now and it freed ~55GiB of a running isntance (the one with 128 GiB allocated). However that should only free blocks of the LV used to store that VM disk, right? And the issue itself is that the sum of maximum allocations of those disks is much lower than the space occupied. I also have the feeling that those blocks remain used by a no longer existant LVs, but I don't know how to fix it. Should I also enable trim/execute trim on Proxmox itself? Oscar