On 2016-12-01 05:14, Andrei Borzenkov wrote:
01.12.2016 07:05, Carlos E. R. пишет:
(the password for the encrypted disk is in a file on the encrypted home partition, so that part was not a surprise)
Could you send me output of
systemctl show '*'
Sure, but it has 9832 lines. Better I email that direct to you.
Id=systemd-cryptsetup@cr_hoard2.service WantedBy=dev-disk-by\x5cx2duuid-24f77e79\x5cx2d947e\x5cx2d4025\x5cx2d8d71\x5cx2d5816411e669d.device
What is device with UUID 24f77e79-947e-4025-8d71-5816411e669d?
Isengard:~ # l /dev/disk/by-uuid/ | grep 24f77e79-947e-4025-8d71-5816411e669d lrwxrwxrwx 1 root root 10 Nov 30 22:36 24f77e79-947e-4025-8d71-5816411e669d -> ../../sdb1 Isengard:~ # Yes, that's my encrypted disk.
But anyway, this is the same pattern. Device actively pulls in cryptsetup.
Yes, if the intention is to mount those entries listed in fstab at boot time, but anytime the device appears, it certainly does so. The disk is encrypted and has an entry in /etc/crypttab, so it is no surprise that it also mounts it: cr_hoard2 /dev/disk/by-uuid/24f77e79-947e-4025-8d71-5816411e669d /home/cer/Keys/the_hoard_keyfile auto See? That's the uuid. As soon as it appears, it creates the corresponding devmapper device, which in turns triggers its mount. So, it works as intended, but not as /I/ intended. ;-)
P.S. apparently we also have double escaping but it's another issue.
Well... -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)