DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] How can a passphrase be incorrect even after `luksHeaderBackup` and `luksHeaderRestore`?
Date: Fri, 05 Aug 2011 19:47:10 +0200	[thread overview]
Message-ID: <4E3C2C9E.9070601@redhat.com> (raw)
In-Reply-To: <20110805145229.GB15345@tansi.org>

On 08/05/2011 04:52 PM, Arno Wagner wrote:
> On Fri, Aug 05, 2011 at 04:16:47PM +0200, Milan Broz wrote:
>> On 08/05/2011 02:11 PM, Paul Menzel wrote:
>>>> No, as from the output above, I do not see the same problem. What
>>>> could be the reason for this difference in behaviour?
>>>
>>> On #lvm Milan suggested that the problem lies with the new drive
>>> having some misalignment
>>
>> I have checked the dump and there is clear corruption of first keyslot
>> (0x1000 - 0x1400 offset).
>>
>> I'll try to find the source of problem now.
>>
>> Milan
> 
> Hi Milan,
> 
> just a thought: May this be a stray v1.2 RAID/md superblock?
> They are at 4k offset from the device start according to this:

yes, but not the superblock but the RAID1 bitmap. even mdadm --zero-superblock
keep the RAID1 bitmap intact.
With MD format 1.2 it is exactly area where I see it now.

So, the first question: what was "cat /proc/mdstat" when doing luksHeaderRestore
(which apparently failed)? Was that drive still in use in some raid?

Milan

  parent reply	other threads:[~2011-08-05 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 21:31 [dm-crypt] How can a passphrase be incorrect even after `luksHeaderBackup` and `luksHeaderRestore`? Paul Menzel
2011-08-04 23:18 ` Paul Menzel
2011-08-05  2:20   ` Milan Broz
2011-08-05  8:41     ` Paul Menzel
2011-08-05 12:11       ` Paul Menzel
2011-08-05 14:16         ` Milan Broz
2011-08-05 14:52           ` Arno Wagner
2011-08-05 14:55             ` Arno Wagner
2011-08-05 17:47             ` Milan Broz [this message]
2011-08-05 15:02           ` Paul Menzel
2011-08-05 15:08             ` Arno Wagner
2011-09-01 19:08           ` Paul Menzel

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=4E3C2C9E.9070601@redhat.com \
    --to=mbroz@redhat.com \
    --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