The test occasionally fails as the umount is not yet completed when cryptsetup close is invoked. Both cryptsetup and losetup have supported deferred cleanup for some time now, so use it instead to avoid races. ++ losetup -P --show --find /tmp/test-repart.dMOfYQ8UUF/zzz + LOOP=/dev/loop6 + VOLUME=test-repart-11882 + touch /tmp/test-repart.dMOfYQ8UUF/empty-password + cryptsetup open --type=luks2 --key-file=/tmp/test-repart.dMOfYQ8UUF/empty*** test-repart-11882 + mkdir /tmp/test-repart.dMOfYQ8UUF/mount + mount -t ext4 /dev/mapper/test-repart-11882 /tmp/test-repart.dMOfYQ8UUF/mount + diff -r /tmp/test-repart.dMOfYQ8UUF/mount/def /tmp/test-repart.dMOfYQ8UUF/definitions + umount /tmp/test-repart.dMOfYQ8UUF/mount + cryptsetup close test-repart-11882 Device test-repart-11882 is still in use. + rm -rf /tmp/test-repart.dMOfYQ8UUF
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
