The symlink /dev/mapper/dm_name is created by udev after a mapper device is set up. So libdevmapper/libcrypsetup might tell us that a verity device exists, but the symlink we use as the source for the mount operation might not be there yet. Instead of falling back to a new unique device set up, wait for the udev event matching on the expected devlink for at least 100ms (after which the benefits of sharing a device in terms of setup time start to disappear - on my production machines, opening a new verity device seems to take between 150ms and 300ms)
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.
