From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from v1.tansi.org (mail.tansi.org [84.19.178.47]) by mail.server123.net (Postfix) with ESMTP for ; Mon, 29 Jul 2019 11:28:53 +0200 (CEST) Received: from gatewagner.dyndns.org (81-6-44-245.init7.net [81.6.44.245]) by v1.tansi.org (Postfix) with ESMTPA id D78A61400D2 for ; Mon, 29 Jul 2019 11:28:49 +0200 (CEST) Date: Mon, 29 Jul 2019 11:28:52 +0200 From: Arno Wagner Message-ID: <20190729092852.GA16338@tansi.org> References: <1590255742.9.1564314256863.JavaMail.gkos@xpska> <265658862.16.1564315066873.JavaMail.gkos@xpska> <20190728210048.GB6115@tansi.org> <48c178d9-b900-cbe6-362f-8faa1c6b435c@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48c178d9-b900-cbe6-362f-8faa1c6b435c@web.de> Subject: Re: [dm-crypt] LUKS Header crruption List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.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