From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH zfsonlinux v2] patches: fix for zvol sync/flush regression
Date: Sun, 16 Mar 2025 20:23:37 +0100 [thread overview]
Message-ID: <20100ae5-2910-4e81-a02b-6352255219ec@proxmox.com> (raw)
In-Reply-To: <20250313113214.23456-1-f.gruenbichler@proxmox.com>
On 13/03/2025 12:32, Fabian Grünbichler wrote:
> this broke with 2.2.7, and can potentially cause data loss or
> inconsistency. the patch basically reverts to pre-2.2.7 behaviour,
> verified via a fio benchmark.
>
> reported on our forum: https://forum.proxmox.com/threads/163066
>
> cherry-picked from upstream master
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> Tested-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> Reviewed-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> v2: added Stoiko's T-b/R-b, replaced patch with equivalent upstream
> master one
>
> ...vols-correctly-detect-flush-requests.patch | 63 +++++++++++++++++++
> debian/patches/series | 1 +
> 2 files changed, 64 insertions(+)
> create mode 100644 debian/patches/0012-linux-zvols-correctly-detect-flush-requests.patch
>
>
applied, with commit subject slightly altered (patches: tag IMO does not give
me as dev nor users if copied in d/changelog much value here), thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-03-16 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 11:32 [pve-devel] " Fabian Grünbichler
2025-03-16 19:23 ` Thomas Lamprecht [this message]
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=20100ae5-2910-4e81-a02b-6352255219ec@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@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