From: Roland <devzero@web.de>
To: linux-raid@vger.kernel.org
Subject: status of bugzilla #99171 - mdraid broken for O_DIRECT
Date: Wed, 9 Oct 2024 22:08:41 +0200 [thread overview]
Message-ID: <5f25dea4-41f6-4bf2-aeed-deb9d8c76e29@web.de> (raw)
Hello,
as proxmox hypervisor does not offer mdadm software raid at installation
time because of this bugticket
"MD RAID or DRBD can be broken from userspace when using O_DIRECT"
https://bugzilla.kernel.org/show_bug.cgi?id=99171
i tried to find some more references besides the kernel bugzilla entry -
and - besides some discussion in the proxmox community - i did not succeed.
why is this apparent fundamental design flaw (should we call it that?)
so damn unknown ?
and what about O_DIRECT with other software raid solutions like btrfs or
zfs ?
how/why do they right but not mdraid ? the latter exists for much
longer time and afaik is offered as install-time option for RHEL
(enterprise linux) for example, where people use oracle on top - which
IS using O_DIRECT very often/likely.
not accusing anyone - just being curious why totally unknown/unpopular
bugticket #99171 bitrots for nearly a decade now...
regards
Roland
Sysadmin
ps:
also see "qemu cache=none should not be used with mdadm"
https://bugzilla.proxmox.com/show_bug.cgi?id=5235
next reply other threads:[~2024-10-09 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 20:08 Roland [this message]
2024-10-09 21:38 ` status of bugzilla #99171 - mdraid broken for O_DIRECT Reindl Harald
2024-10-10 6:53 ` Hannes Reinecke
2024-10-10 7:29 ` Roland
2024-10-10 8:34 ` Hannes Reinecke
2025-10-11 19:25 ` Roland
2025-10-13 6:48 ` Hannes Reinecke
2025-10-13 19:06 ` Roland
[not found] ` <6fb3e2cb-8eeb-4e76-9364-16348d807784@web.de>
2025-10-14 6:31 ` Hannes Reinecke
[not found] <A4168F21-4CDF-4BAD-8754-30BAA1315C6F@web.de>
2025-10-14 20:14 ` Roland
2025-10-15 6:56 ` Hannes Reinecke
2025-10-15 23:09 ` Roland
2025-10-16 6:02 ` Hannes Reinecke
2025-10-17 20:18 ` Roland
2025-10-20 6:44 ` Hannes Reinecke
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=5f25dea4-41f6-4bf2-aeed-deb9d8c76e29@web.de \
--to=devzero@web.de \
--cc=linux-raid@vger.kernel.org \
/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