From: JeffleXu <jefflexu@linux.alibaba.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
joseph.qi@linux.alibaba.com
Subject: Re: [PATCH RFC 1/2] xfstests: fsx: add support for cluster size
Date: Wed, 29 Apr 2020 15:22:49 +0800 [thread overview]
Message-ID: <66363e66-9c89-b877-e8d5-830d2c100b3b@linux.alibaba.com> (raw)
In-Reply-To: <20200427172929.GL6740@magnolia>
On 4/28/20 1:29 AM, Darrick J. Wong wrote:
> On Fri, Apr 24, 2020 at 05:33:49PM +0800, Jeffle Xu wrote:
>> The offset and size should be aligned with cluster size when inserting
>> or collapsing range on ext4 with 'bigalloc' feature enabled. Currently
>> I can find only ext4 with this limitation.
> ocfs2 also has this magic, um, ability.
>
> As does xfs under certain circumstance (realtime volumes).
>
>> Since fsx should have no assumption of the underlying filesystem, and
>> thus add the '-u cluster_size' option. Tests can set this option when
>> the underlying filesystem is ext4 with bigalloc enabled.
> Do copyrange, clonerange, or deduperange have this problem? ;)
clonerange and deduperange are not supported in ext4, while copyrange
and zerorange work as the range has no need to be aligned with cluster size
in these two situations.
next prev parent reply other threads:[~2020-04-29 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 9:33 [PATCH RFC 0/2] fsx: make fsx perceptive to cluster size Jeffle Xu
2020-04-24 9:33 ` [PATCH RFC 1/2] xfstests: fsx: add support for " Jeffle Xu
2020-04-27 17:29 ` Darrick J. Wong
2020-04-29 7:22 ` JeffleXu [this message]
2020-04-24 9:33 ` [PATCH RFC 2/2] xfstests: common/rc: add cluster size support for ext4 Jeffle Xu
2020-04-27 17:33 ` Darrick J. Wong
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=66363e66-9c89-b877-e8d5-830d2c100b3b@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-ext4@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