https://bugzilla.novell.com/show_bug.cgi?id=742774
https://bugzilla.novell.com/show_bug.cgi?id=742774#c4
Till Dörges
encrypting twice is overkill IMHO.
All data and most of the system (everything w/o /boot) has to be encrypted, if the machine is powered off. Using LVM encryption offered by YaST is the perfect choice. But there's data that I only need once in a while. So I want to decrypt it manually just when I need it.
Are you sure you are using encrypted file and not partition ? If so, this is fixed in 12.1 maintenance update for systemd.
I'm not using files. What I wrote in comment #2 was the direct output of `file': box:~ # file -s /dev/sda3 /dev/sda3: LUKS encrypted file, ver 1 [aes, cbc-essiv:sha256, sha1] UUID: 85f45748-165a-4347-944c-a709e6080ad4 box:~ # file -s $(readlink -f /dev/mapper/cr_sda3) /dev/dm-0: LVM2 PV (Linux Logical Volume Manager), UUID: q9STIc-nObd-GjDo-Z55I-LOxL-4FEt-QeS5mc, size: 689582374912 box:~ # file -s $(readlink -f /dev/system/crypt1) /dev/dm-5: LUKS encrypted file, ver 1 [aes, cbc-essiv:sha256, sha1] UUID: 94b7650b-393b-419d-86e9-4f2dde29d904 box:~ # file -s $(readlink -f /dev/mapper/cr_mnt1) /dev/dm-7: Linux rev 1.0 ext4 filesystem data, UUID=5f30fc0f-2739-497f-a6c3-04515d63263d (needs journal recovery) (extents) (large files) (huge files) I'll attach a detailed version (output of fdisk, mount, lvdisplay etc.) The issue still persists. I'm using these versions: $ rpm -qa | grep systemd | sort systemd-37-3.8.1.x86_64 systemd-presets-branding-openSUSE-0.1.0-6.2.1.noarch systemd-sysvinit-37-3.8.1.x86_64 (In reply to comment #1)
could you reboot with "systemd.log_level=debug systemd.log_target=kmsg" and attach dmesg output ?
Also see attachment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.