public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Marco Gaiarin <gaio@lilliput.linux.it>
To: "Daniel Plominski" <dpl@ass.de>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Force reclaiming space on a vdisk...
Date: Thu, 20 Jan 2022 11:47:28 +0100	[thread overview]
Message-ID: <u6rnbi-53d.ln1@hermione.lilliput.linux.it> (raw)
In-Reply-To: <em43fe74a4-b39a-4e87-9a48-08120dd8efeb@1982bcd5.com>; from SmartGate on Thu, Jan 20, 2022 at 12:06:02PM +0100

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)





  reply	other threads:[~2022-01-20 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19  8:19 Marco Gaiarin
2022-01-19  8:49 ` Daniel Plominski
2022-01-20 10:47   ` Marco Gaiarin [this message]
     [not found]     ` <qmMMMDznVErHvtLDASvXi93ArFgsrEDwDgYRRb1tvWRv7rmQTETQI8owpr6NthnRc4Ti1mgm4XjK-QciST-hyaWdPwjq2OpIc_7yEM5_b0Q=@protonmail.ch>
2022-01-20 12:23       ` Daniel Plominski
     [not found]     ` <mailman.129.1642678747.436.pve-user@lists.proxmox.com>
2022-01-21 10:03       ` Marco Gaiarin
2022-01-25 10:44         ` 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=u6rnbi-53d.ln1@hermione.lilliput.linux.it \
    --to=gaio@lilliput.linux.it \
    --cc=dpl@ass.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal