From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: kreijack@inwind.it, Qu Wenruo <wqu@suse.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
zfs-devel@list.zfsonlinux.org
Subject: Re: Ideas for RAIDZ-like design to solve write-holes, with larger fs block size
Date: Sat, 29 Nov 2025 07:00:06 +1030 [thread overview]
Message-ID: <e04e525f-8cc1-42c1-b234-e74e06d91446@gmx.com> (raw)
In-Reply-To: <466de455-a413-424f-9853-7d7d10abce49@inwind.it>
在 2025/11/29 06:51, Goffredo Baroncelli 写道:
> On 28/11/2025 21.10, Qu Wenruo wrote:
[...]
>>> As wrote above, I suggests to use a "per chunk" fs-bs
>>
>> As mentioned, bs must be per-fs, or writes can not be ensured to be bs
>> aligned.
>
>
> Ok.. try to see from another POV: may be that it would be enough that
> the allocator ... allocates space for extent with a specific multiple
> of ps ?
> This and the fact that an extent is immutable, should be enough...
Nope, things like relocation can easily break the immutable assumption.
That's why I don't think it's even possible to implement a per-chunk
stripe length, as that will make some extent that's totally bs aligned
to be not aligned on another chunk.
Thanks,
Qu
prev parent reply other threads:[~2025-11-28 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 3:07 Ideas for RAIDZ-like design to solve write-holes, with larger fs block size Qu Wenruo
2025-11-28 19:49 ` Goffredo Baroncelli
2025-11-28 20:10 ` Qu Wenruo
2025-11-28 20:21 ` Goffredo Baroncelli
2025-11-28 20:30 ` Qu Wenruo [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=e04e525f-8cc1-42c1-b234-e74e06d91446@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=wqu@suse.com \
--cc=zfs-devel@list.zfsonlinux.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;
as well as URLs for NNTP newsgroup(s).