From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: linstor-proxmox v8.1.0-rc.1
Date: Wed, 8 Jan 2025 14:51:10 +0100 [thread overview]
Message-ID: <Z36CzmqSHG4_aSiA@arm64> (raw)
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
Dear DRBD on PVE users,
this is the first RC for the upcoming 8.1.0 release. So far the plugin
did not announce "sparesinit" for volumes that are on backing devices
that are guaranteed to read 0s. The effect was that disk clones to such
resources became thick. Now such clones should be thin (i.e., when all
backing devices are on LVM_THIN/ZFS_THIN storage providers in LINSTOR).
Please test, packages are available in our public staging repos. If we
don't find any bugs, I will release 8.1.0 in about a week from now.
Regards, rck
GIT: https://github.com/LINBIT/linstor-proxmox/commit/405146e5c454273cd7fb1175114e6f55ce05206a
TGZ: https://pkg.linbit.com//downloads/connectors/linstor-proxmox-8.1.0-rc.1.tar.gz
Changelog:
[ Roland Kammerer ]
* set 'sparseinit' feature
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2025-01-08 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Z36CzmqSHG4_aSiA@arm64 \
--to=roland.kammerer@linbit.com \
--cc=drbd-announce@lists.linbit.com \
--cc=drbd-user@lists.linbit.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