From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from blaine.gmane.org (unknown [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Mon, 10 Apr 2017 23:29:30 +0200 (CEST) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cxgsE-0007Xe-Vb for dm-crypt@saout.de; Mon, 10 Apr 2017 23:29:22 +0200 From: Robert Nichols Date: Mon, 10 Apr 2017 16:29:20 -0500 Message-ID: References: <88aa0744-52bb-6b4a-dd09-667e798f3927@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: Subject: Re: [dm-crypt] Detached headers, multiple drives and UUIDs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 04/10/2017 03:53 PM, 7heo wrote: > On Mon Apr 10 21:10:51 2017 GMT+0200, Milan Broz wrote: >> And the activated device-mapper UUID is something else - it is constructed >> as LUKS prefix plus LUKS header UUID plus activated name (then cannot >> be the same). > > Then I have to try to fetch the device mapper again, because that was what caused all this. I assumed that the device-mapper UUID was directly derivated from the LUKS UUID. The UUID reported by "blkid" and "lsblk -f" is _exactly_ the luksUUID. The UUID reported by "dmsetup info" is the luksUUID prefixed by "CRYPT-LUKS1-" and suffixed by "-{mapper_name}". If you leave the UUID the same, the output from "blkid" and "lsblk -f" will be confusing. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.