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.
