For btrfs, if compression is enabled, it may generate inline data for a blocksize data range, this inline data is stored in fs tree, will not have a individual extent, try to reflink this data range at a not-zero offset will return EOPNOTSUPP, so here we disable inline data feature for btrfs.
Signed-off-by: Wang Xiaoguang <wangxg.f...@cn.fujitsu.com> --- tests/generic/175 | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/tests/generic/175 b/tests/generic/175 index 964580c..b3f90dc 100755 --- a/tests/generic/175 +++ b/tests/generic/175 @@ -50,6 +50,13 @@ rm -f "$seqres.full" echo "Format and mount" _scratch_mkfs > "$seqres.full" 2>&1 +# For btrfs, if compression is enabled, it may generate inline data for a +# blocksize data range, this inline data is stored in fs tree, will not have +# a individual extent, try to reflink this data range at a not-zero offset +# will return EOPNOTSUPP, so here we disable inline data feature for btrfs. +if [ "$FSTYP" = "btrfs" ]; then + export MOUNT_OPTIONS="-o max_inline=0 $MOUNT_OPTIONS" +fi _scratch_mount >> "$seqres.full" 2>&1 testdir="$SCRATCH_MNT/test-$seq" -- 2.9.0 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
