public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Roland <devzero@web.de>, Reindl Harald <h.reindl@thelounge.net>,
	linux-raid@vger.kernel.org
Subject: Re: status of bugzilla #99171 - mdraid broken for O_DIRECT
Date: Thu, 16 Oct 2025 08:02:34 +0200	[thread overview]
Message-ID: <92bc9643-53fe-4c56-abdd-7a9efb451f1c@suse.de> (raw)
In-Reply-To: <fd968202-04aa-48e3-bbd7-8520570d1ae2@web.de>

On 10/16/25 01:09, Roland wrote:
[ .. ]>
> thank you for your feedback.
> 
> i see, things are complicated and O_DIRECT is a very special beast....
> 
> meanwhile, i gave bcachefs a try today , because it looks interesting .
> 
> like zfs, it does not seem to be affected by this problem, at least from 
> my first tests reported at https://bugzilla.kernel.org/show_bug.cgi? 
> id=99171#c26 (i hope this is a valid test for consistency)
> 
> so we have at least a second "software raid" technology besides zfs, 
> which does NOT suffer from the "by design" O_DIRECT breakage.
> 
> that's at least surprising me, as bcachefs is far from production 
> ready,  and i wonder why it just seems to work at this early stage of 
> development.
> 
Hmm. True.

I would suggest bringing up this topic on linux-fsdevel; there is
always a chance that there is a bug somewhere.
At least some explanation would be warranted why bcachefs does not
suffer from this issue.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
hare@suse.de                                +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich

  reply	other threads:[~2025-10-16  6:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A4168F21-4CDF-4BAD-8754-30BAA1315C6F@web.de>
2025-10-14 20:14 ` status of bugzilla #99171 - mdraid broken for O_DIRECT Roland
2025-10-15  6:56   ` Hannes Reinecke
2025-10-15 23:09     ` Roland
2025-10-16  6:02       ` Hannes Reinecke [this message]
2025-10-17 20:18         ` Roland
2025-10-20  6:44           ` Hannes Reinecke
2024-10-09 20:08 Roland
2024-10-09 21:38 ` 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

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=92bc9643-53fe-4c56-abdd-7a9efb451f1c@suse.de \
    --to=hare@suse.de \
    --cc=devzero@web.de \
    --cc=h.reindl@thelounge.net \
    --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