From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wj0-x242.google.com (mail-wj0-x242.google.com [IPv6:2a00:1450:400c:c01::242]) (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 ; Fri, 30 Dec 2016 03:18:10 +0100 (CET) Received: by mail-wj0-x242.google.com with SMTP id j10so59396248wjb.3 for ; Thu, 29 Dec 2016 18:18:10 -0800 (PST) References: From: Milan Broz Message-ID: Date: Fri, 30 Dec 2016 03:18:06 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Cryptsetup bug List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hunter DeMeyer , dm-crypt@saout.de On 12/29/2016 06:53 PM, Hunter DeMeyer wrote: > I believe that under certain circumstances cryptsetup will encrypt > more than one partion on a drive. I have attached the process that > produced this bug. Cryptsetup accesses only device that you specify. There are two options how could happen that LUKS device appeared on different partition: 1) there was some old LUKS device on the /dev/sdb1 offset start already or 2) you recreated partitions but for some reason kernel still see the old partitions size, and sdb1 was still in fact mapped to the old partition. Could you please paste blkid /dev/sdb* to verify it is the first option (to check LUKS UUID)? I guess you will see different UUIDs. And please do not send html mails to the list. Milan