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 DA33962462 for ; Thu, 20 Jan 2022 12:10:19 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D0CCF23B6B for ; Thu, 20 Jan 2022 12:10:19 +0100 (CET) Received: from picard.linux.it (picard.linux.it [IPv6:2001:1418:10:5::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 06B5723B5C for ; Thu, 20 Jan 2022 12:10:19 +0100 (CET) Received: by picard.linux.it (Postfix, from userid 10) id A66193C96A1; Thu, 20 Jan 2022 12:10:12 +0100 (CET) Received: from news by eraldo.lilliput.linux.it with local (Exim 4.89) (envelope-from ) id 1nAVGU-0006SQ-4e for pve-user@lists.proxmox.com; Thu, 20 Jan 2022 12:06:02 +0100 From: Marco Gaiarin Date: Thu, 20 Jan 2022 11:47:28 +0100 Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!! Message-ID: References: X-Trace: eraldo.lilliput.linux.it 1642676154 22884 192.168.24.2 (20 Jan 2022 10:55:54 GMT) To: "Daniel Plominski" X-Mailer: tin/2.4.4-20191224 ("Millburn") (Linux/5.4.0-96-generic (x86_64)) X-Gateway-System: SmartGate 1.4.5 Cc: pve-user@lists.proxmox.com In-Reply-To: ; from SmartGate on Thu, Jan 20, 2022 at 12:06:02PM +0100 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.008 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% JMQ_SPF_NEUTRAL 0.5 SPF set to ?all 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 Subject: Re: [PVE-User] Force reclaiming space on a vdisk... 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: Thu, 20 Jan 2022 11:10:19 -0000 Mandi! Daniel Plominski In chel di` si favelave... > enable ZFS set compression=lz4 on the zvolume Seems just enabled: root@ctpve1:~# zpool get all rpool | grep lz4 rpool feature@lz4_compress active local root@ctpve1:~# zpool get all rpool-data | grep lz4 rpool-data feature@lz4_compress active local > and perform a memory limit dd run (inside the vm). > dd if=/dev/zero of=/mountpoint_sda7/CLEANUP bs=99M count=xxx > (this will release the storage space) OK. But i've just deleted the partitions. I have to create a new partition, format them, create a 'dd-zero' file in them and then the space will be released? Really?! I'm asking because i supposed that was the 'trim/thin' feature of ZFS to permit to shrink a disk (eg, 'don't save the unallocated space'), not the compressione feature (eg, 'don't save a bunch of consecutive zero, compress it'). Speaking more clearly, i hope: i've perfectly clear that 'zeroing' a portion of a disk permit the compression feature of zfs to compress it, but i supposed that was the management of allocated spaces that make their business here... i'm only a bit puzzled. I hope someone can clarify, thanks. PS: this server have a 'Proxmox VE Community Subscription 1 CPU/year' currently active on, but i prefere if possible to use mailing list for this support question. FYI. -- Ognuno vada dove vuole andare, ognuno invecchi come gli pare ma non raccontate a me che cos'e` la LIBERTA`. (F. Guccini)