mirror of
https://github.com/morgan9e/systemd
synced 2026-04-16 01:16:10 +09:00
0ae4456c93
Since systemd 206 the combination of systemd and mkinitcpio causes, under certain conditions, the rootfs to be double fsck'd. Symptoms: ``` :: performing fsck on '/dev/sda1' systemd: clean, 3523/125488 files, 141738/501760 blocks ********************** WARNING ********************** * * * The root device is not configured to be mounted * * read-write! It may be fsck'd again later. * * * ***************************************************** <snip> [ OK ] Started File System Check on Root Device ``` This occurs when neither 'ro' or 'rw', or only 'ro' is present on the kernel command line. The solution is to mount the roofs as read-write on the kernel command line, so systemd knows to not fsck it again.
The extended testsuite only works with UID=0. It contains of several subdirectories named "test/TEST-??-*", which are run one by one. To run the extended testsuite do the following: $ ninja -C build # Avoid building anything as root later $ sudo test/run-integration-tests.sh ninja: Entering directory `/home/zbyszek/src/systemd/build' ninja: no work to do. --x-- Running TEST-01-BASIC --x-- + make -C TEST-01-BASIC BUILD_DIR=/home/zbyszek/src/systemd/build clean setup run make: Entering directory '/home/zbyszek/src/systemd/test/TEST-01-BASIC' TEST CLEANUP: Basic systemd setup TEST SETUP: Basic systemd setup ... TEST RUN: Basic systemd setup [OK] make: Leaving directory '/home/zbyszek/src/systemd/test/TEST-01-BASIC' --x-- Result of TEST-01-BASIC: 0 --x-- --x-- Running TEST-02-CRYPTSETUP --x-- + make -C TEST-02-CRYPTSETUP BUILD_DIR=/home/zbyszek/src/systemd/build clean setup run If one of the tests fails, then $subdir/test.log contains the log file of the test. To run just one of the cases: $ sudo make -C test/TEST-01-BASIC clean setup run Specifying the build directory ============================== If the build directory is not detected automatically, it can be specified with BUILD_DIR=: $ sudo BUILD_DIR=some-other-build/ test/run-integration-tests or $ sudo make -C test/TEST-01-BASIC BUILD_DIR=../../some-other-build/ ... Note that in the second case, the path is relative to the test case directory. An absolute path may also be used in both cases. Configuration variables ======================= TEST_NO_QEMU=1 can be used to disable qemu tests. TEST_NO_NSPAWN=1 can be used to disable nspawn tests. KERNEL_APPEND='...' can be used to add additional kernel parameters for the QEMU runs. The kernel and initramfs can be specified with $KERNEL_BIN and $INITRD. (Fedora's or Debian's default kernel path and initramfs are used by default) A script will try to find your QEMU binary. If you want to specify a different one with $QEMU_BIN. Debugging the qemu image ======================== If you want to log in the testsuite virtual machine, you can specify additional kernel command line parameter with $KERNEL_APPEND and then log in as root. $ sudo make -C test/TEST-01-BASIC KERNEL_APPEND="systemd.unit=multi-user.target" run Root password is empty.