[Bug 474258] Re: Extremely dangerous! cryptswap killed my partition
Cezary Baginski
474258 at bugs.launchpad.net
Sat Feb 4 18:34:33 UTC 2012
@Tuomas:
I agree - LVM is a cleaner solution (although at first, I thought the
lvm handling would need too much code).
Good points about linking and /dev/dm*.
@bugfix
It turns out there is an obvious bug with detecting filesystems before
running mkswap.
My take on fixing it:
https://code.launchpad.net/~cezary0/cryptsetup/bugfix474258
The patch probably applies cleanly to almost every version, so you can
apply it locally already.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
Status in “cryptsetup” package in Ubuntu:
Triaged
Status in “cryptsetup” source package in Precise:
Triaged
Status in “cryptsetup” package in Debian:
New
Bug description:
Binary package hint: cryptmount
9.10 installed with encrypted "home".
Had root on /dev/sda1, swap on /dev/sda2, and manually created "data" partition on "/dev/sda3"
When I deleted /dev/sda2 partition (wanted to move swap to the second HDD) - ubuntu killed my "data" partition!
I suppose the problem is that /dev/sda3 became /dev/sda2 and the cryptswap utility just killed all the data (about 80 gigs!), because /dev/sda2 is in the /etc/crypttab file as a swap partition...
Cryptswap should check the type of partition before mounting it as swap.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/474258/+subscriptions
More information about the foundations-bugs
mailing list