From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Alwin Antreich via pve-user <pve-user@lists.proxmox.com>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Analysis of free space...
Date: Mon, 6 Oct 2025 13:32:45 +0200 [thread overview]
Message-ID: <rvlcrl-s2b1.ln1@leia.lilliput.linux.it> (raw)
In-Reply-To: <mailman.555.1759327422.390.pve-user@lists.proxmox.com>; from SmartGate on Mon, Oct 06, 2025 at 23:06:02PM +0200
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
next prev parent reply other threads:[~2025-10-06 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 13:27 Marco Gaiarin
2025-09-17 23:45 ` Gilou
2025-09-22 14:14 ` Marco Gaiarin
2025-09-22 14:17 ` Marco Gaiarin
2025-09-24 16:29 ` Marco Gaiarin
2025-09-27 15:42 ` Alwin Antreich via pve-user
2025-09-30 16:26 ` Marco Gaiarin
2025-09-27 16:06 ` Matthieu Dreistadt via pve-user
2025-09-30 16:55 ` Marco Gaiarin
2025-10-01 14:03 ` Alwin Antreich via pve-user
2025-10-06 11:32 ` Marco Gaiarin [this message]
2025-09-26 14:57 ` Marco Gaiarin
2025-09-18 13:44 ` Alwin Antreich via pve-user
2025-09-22 14:16 ` Marco Gaiarin
2025-09-25 8:26 ` Marco Gaiarin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rvlcrl-s2b1.ln1@leia.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.