Closed vr00m closed 4 years ago
The eternal wait happens at the last dm_udev_wait(cookie)
in "tcplay.c" line 1846. It's probably some problem in the "udev" rules. Executing udevadm monitor --udev --env
shows that the DM-device is being successfully created but some post actions are missing and dm_udev_wait(cookie)
waits forever.
If I comment out the last dm_udev_wait(cookie)
in "tcplay.c" and recompile, then the mount succeeds with the following warning:
/dev/mapper/backup17 not set up by udev: Falling back to direct node creation.
Here "backup17" is the mapping name that I chose for my encrypted block device.
I managed to get the Ubuntu/Debian package working as well. You need to additionally install dmsetup
:
apt-get install dmsetup
This package installs the following "udev" rules which probably resolve the issue:
/lib/udev/rules.d/55-dm.rules
/lib/udev/rules.d/60-persistent-storage-dm.rules
@bwalex, maybe you can mention in the README that apt-get install dmsetup
is required for the latest Debian/Ubuntu systems.
Ubuntu packaging bug: https://bugs.launchpad.net/ubuntu/+source/tcplay/+bug/1625822
This seems like a distro package problem - that's where the dependency should be defined.
I experienced the same issue mentioned here After interrupting the hung tcplay, I was unable to detach the encrypted file from the loop device:
sudo losetup -d /dev/loop0
(returns the prompt, with no errors)But,
lsof | grep loop0
returnsand,
kill -9 2465
does not work