From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Expanding a LUKS partition to a second drive.
Date: Wed, 12 Feb 2020 13:15:52 -0600 [thread overview]
Message-ID: <r21it9$34pk$1@ciao.gmane.io> (raw)
In-Reply-To: <0eaccf2a-dd30-1b8f-436f-25dd64ac58a9@redhat.com>
On 2/12/20 9:01 AM, Ondrej Kozina wrote:
> On 2/12/20 3:29 PM, Robert Nichols wrote:
>> On 2/12/20 4:45 AM, Ondrej Kozina wrote:
>>> On 2/11/20 8:21 PM, James Dehnert wrote:
>>>>
>>>> I'm not sure where the LUKS volume is created in respect to LVM. I can't tell if its created directly on the physical volume, on the volume group, or on the logical volume, so I'm noy sure where I should be looking to expand the substrate. Or if this is even possible.
>>>
>>> See lsblk output with said active LUKS device. That should give you a hint.
>>>
>>> If the PV is encrypted (LUKS on top of /dev/sdx and PV on top of LUKS) there's no way how to extend one LUKS device over two devices or partitions. We don't want cryptsetup to became yet another logical volume management:)
>>
>> True, but it's simple enough to create a second LUKS volume and extend an existing LVM VG into that LUKS volume.
>
> Sure, but "having multiple LUKS devices" vs "having one LUKS (logical) device managing multiple physical devices" are two completely different problems. Although I agree with you that having two LUKS encrypted PVs would solve this specific problem.
>
> What I'm saying is that cryptsetup will not support managing multiple data devices. I'm inclined to add "ever" to last sentence, but I'm not upstream maintainer:)
I agree 100%. My suggestion was just addressing the current problem.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
next prev parent reply other threads:[~2020-02-12 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 19:21 [dm-crypt] Expanding a LUKS partition to a second drive James Dehnert
2020-02-12 10:45 ` Ondrej Kozina
2020-02-12 14:29 ` Robert Nichols
2020-02-12 15:01 ` Ondrej Kozina
2020-02-12 19:15 ` Robert Nichols [this message]
2020-02-12 16:48 ` Arno Wagner
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='r21it9$34pk$1@ciao.gmane.io' \
--to=rnicholsnospam@comcast.net \
--cc=dm-crypt@saout.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).