From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS Header crruption
Date: Mon, 29 Jul 2019 11:28:52 +0200 [thread overview]
Message-ID: <20190729092852.GA16338@tansi.org> (raw)
In-Reply-To: <48c178d9-b900-cbe6-362f-8faa1c6b435c@web.de>
On Mon, Jul 29, 2019 at 09:25:15 CEST, Uwe Menges wrote:
> On 7/28/19 11:00 PM, Arno Wagner wrote:
> > One of the reasons why I think RAID superblocks at the start of the
> > device (and even more so at 4kB offset) are messed up and a sign
> > of clueless designers.
>
> Depending on the md metadata version, it's either at the start, at the
> end, or 4k from start - each with its own drawbacks. The metadata needs
> to reside somewhere, quite the same as with LUKS, or filesystem
> metadata. If you have a hint on how to get around that, please tell.. :)
Maybe read what I wrote, because you seem to not have done so?
And yes, I am aware of the different problems.
Regards,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2019-07-29 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1590255742.9.1564314256863.JavaMail.gkos@xpska>
2019-07-28 11:57 ` [dm-crypt] LUKS Header crruption Konstantin V. Gavrilenko
2019-07-28 21:00 ` Arno Wagner
2019-07-29 7:25 ` Uwe Menges
2019-07-29 9:28 ` Arno Wagner [this message]
[not found] <1313728220.30.1564401565268.JavaMail.gkos@xpska>
2019-07-29 12:08 ` Konstantin V. Gavrilenko
2019-07-29 13:56 ` Robert Nichols
2019-07-29 14:33 ` Milan Broz
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=20190729092852.GA16338@tansi.org \
--to=arno@wagner.name \
--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