[Top] [All Lists]

[RFC][PATCH 00/10] xfstests: Add support for config section

To: xfs@xxxxxxxxxxx
Subject: [RFC][PATCH 00/10] xfstests: Add support for config section
From: Lukas Czerner <lczerner@xxxxxxxxxx>
Date: Wed, 10 Jul 2013 16:00:29 +0200
Delivered-to: xfs@xxxxxxxxxxx
This patch set adds support for sections in the configuration file
while maintaining unchanged behaviour when no sections are present in the
configuration file, or no configuration file is provided.

Explanation, syntax and example follows.

Configuration file with sections

Configuration file with sections is useful for running xfstests on multiple
file systems, or multiple file system setups in a single run without any
help of external scripts.


Syntax for defining a section is the following:


Section name should consist of alphanumeric characters and '_'. Anything
else is forbidden and the section will not be recognised.

Each section in the configuration file should contain options in the format


'OPTION' must not contain any white space characters. 'value' can contain
any character you want with one simple limitation - characters ' and " can
only appear at the start and end of the 'value', however it is not required.

Note that options are carried between sections so the same options does not
have to be specified in each and every sections. However caution should be
exercised not to leave unwanted options set from previous sections.


For every section xfstests will run with specified options and will produce
separate results in the '$RESULT_BASE/$section_name' directory.

Different mount options

Specifying different mount options in difference config sections is allowed.
When MOUNT_OPTIONS differs in the following section TEST_DEV will be remounted
with new MOUNT_OPTIONS automatically before running the test.

Multiple file systems

Having different file systems in different config sections is allowed. When
FSTYP differs in the following section the FSTYP file system will be created
automatically before running the test.

Note that if MOUNT_OPTIONS, MKFS_OPTIONS, or FSCK_OPTIONS are not directly
specified in the section it will be reset to the default for a given file

You can also force the file system recreation by specifying RECREATE_TEST_DEV.


Here is an example of config file with sections:

MKFS_OPTIONS="-q -F -b4096"
RESULT_BASE="`pwd`/results/`date +%d%m%y_%H%M%S`"

MKFS_OPTIONS="-q -F -b1024"

MKFS_OPTIONS="-q -F -b4096 -O ^has_journal"


MOUNT_OPTIONS="-o noatime"

<Prev in Thread] Current Thread [Next in Thread>