We discussed that in #ubuntu-release. Given how close karmic's release
is, we think this is a viable strategy:
(1) For karmic, patch blkid to prefer luks over ext*
Rationale: This has been the behaviour for years, and worked well.
We also know that creating a luks volume did not properly clean up
traces from a previous ext file system, while we know that creating an
ext file system over a luks file system worked properly. (I'll verify
that again, though)
Reopening an util-linux task for that.
(2) For Lucid, discuss a proper migration strategy to clean up
superblocks on upgrades. This isn't release critical for Karmic any more
then.
Keeping non-karmic cryptsetup task for that.
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Karmic)
Importance: Undecided => High
** Changed in: util-linux (Ubuntu Karmic)
Status: New => In Progress
** Changed in: util-linux (Ubuntu Karmic)
Milestone: None => ubuntu-9.10
** Changed in: util-linux (Ubuntu Karmic)
Assignee: (unassigned) => Martin Pitt (pitti)
** Summary changed:
- luks encrypted partition not detected or mounted automatically
+ luks encrypted partition not detected when it was created over an ext
partition
** Changed in: cryptsetup (Ubuntu Karmic)
Status: Confirmed => Won't Fix
** Changed in: cryptsetup (Ubuntu Karmic)
Importance: High => Undecided
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Triaged
--
luks encrypted partition not detected when it was created over an ext partition
https://bugs.launchpad.net/bugs/428435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
