From: Milan Broz <gmazyland@gmail.com>
To: Two Spirit <twospirit6905@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] gpt over luks - entire data disk encryption
Date: Thu, 19 Jul 2012 10:24:43 +0200 [thread overview]
Message-ID: <5007C44B.9030200@gmail.com> (raw)
In-Reply-To: <CAKRxpuv-YXow3YC4dJvUM9Vs2q8YrJOTtnWzATTUvtLYbFJhLg@mail.gmail.com>
On 07/18/2012 11:46 PM, Two Spirit wrote:
> After some corruptions to my luks environment, I get an opportunity to make some upgrades to my setup.
> I need some help. I'm testing a raid5+1 environment, and would like to do whole data disk encryptions
> with GPT. once I partition the disk using GPT, I can't run the "cryptsetup luksClose". I've done
> whole disk encryption without a partition table with no problems, and I also have done luks encryption
> on a GPT partition without problems.
What's the exact dvice stack here? (paste lsblk output?)
(You have GPT over LUKS device, not directly on /dev/mraid51, correct?
> The only way I have found to be able to run luksClose is to blow away the partition table(which is not
> acceptable solution). I suspect that udevadm (running ubuntu-12.04) is involved as a /dev/mapper/raid51p1
> exists. When I get rid of the /dev/mapper/raid51p1, and only the /dev/mapper/raid51 exists, I can then run "luksClose".
Someone is running kpartx automatically...
/dev/mapper/raid51p1 is created by kpartx (or some internal code somewhere) and it should _not_ be there,
MD can handle partitions in kernel since 2.6.38 kernel.
I see that problem on Fedora 17 as well. I will back to this later, not a LUKS problem but IMHO it is bug.
I guess you can "dmsetup remove raid51p1" to get rid of this before shutdown, but it is wrong.
For me, it even doesn't set DM-UUID (someone wrongly copied code from kpartx seems :-)
Milan
next prev parent reply other threads:[~2012-07-19 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 21:46 [dm-crypt] gpt over luks - entire data disk encryption Two Spirit
2012-07-19 8:24 ` Milan Broz [this message]
2012-07-19 8:43 ` Milan Broz
2012-07-19 11:07 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5007C44B.9030200@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=twospirit6905@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.