Re: [LSF/MM TOPIC] FS, MM, and stable trees

[Luis Chamberlain <mcgrof@kernel.org>]

On Thu, Mar 10, 2022 at 01:51:22PM -0500, Josef Bacik wrote:
> [root@fedora-rawhide ~]# cat /xfstests-dev/local.config
> [btrfs_normal_freespacetree]
> [btrfs_compress_freespacetree]
> [btrfs_normal]
> [btrfs_compression]
> [kdave]
> [btrfs_normal_noholes]
> [btrfs_compress_noholes]
> [btrfs_noholes_freespacetree]

+ linux-btrfs and zone folks.

I simplified these as follows, please let me know if the names are
alright. I think we may be able to come up with something more
clever than btrfs_dave. The raid56/noraid56 exist just for the
defaults of the distro/btrfs-progs. The expunge list is used
to determine if something is raid56 or not sadly given we
have no groups for putting tests into the raid56 group. The idea
is some distros don't support raid56 so that is the goal with
the noraid56 config.

The name needs to be: $FS_$FANCY_SINGLE_SPACED_NAME

Each guest spawned will have that same hostname. And likewise
the expunges are collected for each guest hostname. The hostname
is used to pick the expunge directory so to ensure it reflects
the baseline.

You may want to look at this expunge file:

https://github.com/mcgrof/kdevops/blob/master/workflows/fstests/expunges/opensuse-leap/15.3/btrfs/unassigned/btrfs_noraid56.txt\x02

[default]
TEST_DEV=@FSTESTSTESTDEV@
TEST_DIR=@FSTESTSDIR@
SCRATCH_DEV_POOL="@FSTESTSSCRATCHDEVPOOL@"

SCRATCH_MNT=@FSTESTSSCRATCHMNT@
RESULT_BASE=$PWD/results/$HOST/$(uname -r)

[btrfs_raid56]
MKFS_OPTIONS='-f'
FSTYP=btrfs

[btrfs_noraid56]
MKFS_OPTIONS='-f'
FSTYP=btrfs

[btrfs_normalfreespacetree]
LOGWRITES_DEV=@FSTESTSLOGWRITESDEV@
MKFS_OPTIONS="-K -f -O ^no-holes"
MOUNT_OPTIONS="-o space_cache=v2"
FSTYP=btrfs

[btrfs_compressfreespacetree]
MOUNT_OPTIONS="-o compress=zlib,space_cache=v2"
MKFS_OPTIONS="-K -f -O ^no-holes"

[btrfs_normal]
LOGWRITES_DEV=@FSTESTSLOGWRITESDEV@
MKFS_OPTIONS="-K -O ^no-holes -R ^free-space-tree"
MOUNT_OPTIONS="-o discard=async"

[btrfs_compression]
MOUNT_OPTIONS="-o compress=zstd,discard=async"
MKFS_OPTIONS="-K -O ^no-holes -R ^free-space-tree"

[btrfs_kdave]
MKFS_OPTIONS="-K -O no-holes -R ^free-space-tree"
MOUNT_OPTIONS="-o discard,space_cache=v2"

[btrfs_normalnoholes]
LOGWRITES_DEV=@FSTESTSLOGWRITESDEV@
MKFS_OPTIONS="-K -O no-holes -f -R ^free-space-tree"

[btrfs_compressnoholes]
MKFS_OPTIONS="-K -O no-holes -f -R ^free-space-tree"
MOUNT_OPTIONS="-o compress=lzo"

[btrfs_noholesfreespacetree]
MKFS_OPTIONS="-K -O no-holes -f"
MOUNT_OPTIONS="-o space_cache=v2"

I see nothing for NVMe ZNS.. so how about 

[btrfs_zns]
MKFS_OPTIONS="-f -d single -m single"
TEST_DEV=@FSTESTSTESTZNSDEV@
SCRATCH_DEV_POOL="@FSTESTSSCRATCHDEVZNSPOOL@"

[btrfs_simple]
TEST_DEV=@FSTESTSTESTSDEV@
MKFS_OPTIONS="-f -d single -m single"
SCRATCH_DEV_POOL="@FSTESTSSCRATCHDEVPOOL@"

The idea being btrfs_simple will not use zns drives behind the scenes
but btrfs_zns will.

  Luis