From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 42AD31FF187 for ; Mon, 6 Oct 2025 23:10:16 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BB2FFBAD2; Mon, 6 Oct 2025 23:10:13 +0200 (CEST) From: Marco Gaiarin Date: Mon, 6 Oct 2025 13:32:45 +0200 Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!! Message-ID: References: <5letql-mot2.ln1@leia.lilliput.linux.it> X-Trace: eraldo.lilliput.linux.it 1759783818 3926714 192.168.1.45 (6 Oct 2025 20:50:18 GMT) To: Alwin Antreich via pve-user X-Mailer: tin/2.6.4-20240224 ("Banff") (Linux/6.14.0-33-generic (x86_64)) X-Gateway-System: SmartGate 1.4.5 Cc: pve-user@lists.proxmox.com In-Reply-To: ; from SmartGate on Mon, Oct 06, 2025 at 23:06:02PM +0200 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.336 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DATE_IN_PAST_06_12 1.543 Date: is 6 to 12 hours before Received: date DMARC_PASS -0.1 DMARC pass policy JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Analysis of free space... 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: , Reply-To: Proxmox VE user list MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" Mandi! Alwin Antreich via pve-user In chel di` si favelave... > Hm... I assume you're running a RAIDz1? root@lamprologus:~# zpool status rpool-data pool: rpool-data state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: scrub repaired 0B in 1 days 15:06:52 with 0 errors on Mon Sep 15 15:30:54 2025 config: NAME STATE READ WRITE CKSUM rpool-data ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 scsi-35000c500d2ae07db ONLINE 0 0 0 scsi-35000c500d2ae767f ONLINE 0 0 0 scsi-35000c500e24688cf ONLINE 0 0 0 scsi-35000c500d2af2d43 ONLINE 0 0 0 scsi-35000c500d2aee0df ONLINE 0 0 0 scsi-35000c500d2af4693 ONLINE 0 0 0 scsi-35000c500f9797483 ONLINE 0 0 0 scsi-35000c500d2ae777f ONLINE 0 0 0 scsi-35000c500d2af3e77 ONLINE 0 0 0 errors: No known data errors Yep. > See the link: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_zfs_raid_size_space_usage_redundancy OK. But this can explain some data, not 20TB of not reclaimed space; and, as just stated, if i delete now (after that i've set discard=on on volume property) data, space get correctly reclaimed. There's some way to 'forcibly reclaim data'? -- _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user