From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane-mx.org>
Received: from ciao.gmane.io (ciao.gmane.io [159.69.161.202])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest
 SHA256) (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed, 12 Feb 2020 15:34:58 +0100 (CET)
Received: from list by ciao.gmane.io with local (Exim 4.92)
 (envelope-from <glkdd-dm-crypt@m.gmane-mx.org>) id 1j1t1X-0004Gm-1P
 for dm-crypt@saout.de; Wed, 12 Feb 2020 15:29:55 +0100
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
Date: Wed, 12 Feb 2020 08:29:50 -0600
Message-ID: <r2124u$fn8$1@ciao.gmane.io>
References: <CAE3N1D+_pZNQGwi8O4dP3c_Hv8PMGkqYHieqTsrfXEi0d1_HGQ@mail.gmail.com>
 <0089ec51-ddaa-b572-2b9a-2fdb56b7c1c2@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
In-Reply-To: <0089ec51-ddaa-b572-2b9a-2fdb56b7c1c2@redhat.com>
Content-Language: en-US
Subject: Re: [dm-crypt] Expanding a LUKS partition to a second drive.
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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.

The output from "lsblk -f" would be most helpful here.

The real problem comes when there is currently no LVM involved at all. Converting an existing system to LVM is a fairly convoluted process where the slightest error can be unrecoverable.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.