Launchpad has imported 5 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=87717.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2014-12-25T20:58:35+00:00 Vecu-bosseur wrote: Dear Developpers, My /etc/crypttab contains: cryptswap1 UUID=c836dd13-1b4e-4bfb-9be5-6e5d972aa75a /dev/urandom swap,offset=2048,cipher=aes-cbc-essiv:sha256 And my /etc/fstab contains: /dev/mapper/cryptswap1 none swap sw 0 0 And this worked fine with cryptdisks_start however the option "offset" is not understood by systemd 215. I did change init system from sysvinit to systemd, and now, after 2 reboots, I don't have any swap and my device that had UUID c836dd13-1b4e-4bfb-9be5-6e5d972aa75a has seen its start erased, and thus its UUID itself, as if I had not mentioned an offset=>>0 in crypttab. The use case for "offset=2048" is to be able to use a UUID to identify the partition I want to have encrypted swap on. Not using an offset=>>0 parameter would unconditionally erase the whole partition, including the portion where its UUID is stored. Using any other way to identify a partition can thus cause data loss if I reparttion my disk and forget to update /etc/crypttab. Please make systemd understand the "offset=" paramater of /etc/crypttab. Has this problem been addressed in a subsequent systemd version? Note: related to debian bug #751707 ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751707 ) Thanks, Vecu Bosseur Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/29 ------------------------------------------------------------------------ On 2014-12-26T01:37:53+00:00 zbyszek wrote: It's a long-standing well-known limitation: /* Options Debian's crypttab knows we don't: offset= skip= precheck= check= checkargs= noearly= loud= keyscript= */ Some of those will probably never be implemented (noearly, keyscript, loud, ...), but offset certainly should. Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/30 ------------------------------------------------------------------------ On 2015-04-16T11:53:47+00:00 Martin Pitt wrote: Created attachment 115118 cryptsetup: Implement offset and skip options Simple patch. Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/74 ------------------------------------------------------------------------ On 2015-04-16T11:54:21+00:00 Martin Pitt wrote: Created attachment 115119 reproducer/test script This is the reproducer and test script which I used. Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/75 ------------------------------------------------------------------------ On 2015-04-16T11:57:12+00:00 zbyszek wrote: I think a failure to parse those parameters should be fatal. It's just to dangerous to continue. Also "meatadata" in description :) Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/76 ** Changed in: systemd Status: Unknown => Confirmed ** Changed in: systemd Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/953875 Title: Encrypted swap no longer mounted at bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
