From: "Daniel Plominski" <dpl@ass.de>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Force reclaiming space on a vdisk...
Date: Thu, 20 Jan 2022 12:23:06 +0000 [thread overview]
Message-ID: <emb8ffef85-71d8-4598-a16d-236476fb4c0a@1982bcd5.com> (raw)
In-Reply-To: <qmMMMDznVErHvtLDASvXi93ArFgsrEDwDgYRRb1tvWRv7rmQTETQI8owpr6NthnRc4Ti1mgm4XjK-QciST-hyaWdPwjq2OpIc_7yEM5_b0Q=@protonmail.ch>
Hello,
we have had very bad experience with trim, due to a virtio driver error,
a special release, the trim resulted in a corrupt Windows NTFS file
system.
The bug is fixed in the latest stable VirtIO drivers, but we only use
the legacy method using targeted "dd" (zero) cleanup on Linux / BSD VMs
and on Windows using "fsutil".
From the perspective of the HOST system, a zvolume formatted with
filesystem and stored data is simply a "data container" with
unstructured data (depending on the structure, however, this can be
compressed well).
If now within the VM an area with zeros is written, this zvolume area is
stimulated to overwrite the contained data, the process is compressed
and the occupied blocks are released.
The block free up should also work with the ZFS algorithm "zle".
How often the cells of an SSD / NVME memory are overwritten depends on
the internal intelligence of the firmware / controller of the respective
memory.
TRIM "Discard" (if supported by the hardware, the hypervisor, the
hypervisor driver and the guest OS) can be used to better control this
remapping.
ASS - Der Bildungseinrichter GmbH
Mit freundlichen Grüßen
DANIEL PLOMINSKI
Leitung IT | Head of IT
Telefon 09265 808-151 | Mobil 0151 58026316 | dpl@ass.de
PGP Key: https://pgp.ass.de/dpl@ass.de.asc
PGP Fingerprint: 74DBC06BD9F63187C4DF8934C96585A89CFC10B3
Company Logo
ASS-Einrichtungssysteme GmbH
ASS-Adam-Stegner-Straße 19 | D-96342 Stockheim
Geschäftsführer: Matthias Stegner, Michael Stegner, Ralph Müller
Amtsgericht Coburg HRB 3395 | Ust-ID: DE218715721
Bottom_Line
next prev parent reply other threads:[~2022-01-20 12:23 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
[not found] ` <qmMMMDznVErHvtLDASvXi93ArFgsrEDwDgYRRb1tvWRv7rmQTETQI8owpr6NthnRc4Ti1mgm4XjK-QciST-hyaWdPwjq2OpIc_7yEM5_b0Q=@protonmail.ch>
2022-01-20 12:23 ` Daniel Plominski [this message]
[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=emb8ffef85-71d8-4598-a16d-236476fb4c0a@1982bcd5.com \
--to=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