From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <arno@wagner.name>
Received: from v6.tansi.org (mail.tansi.org [87.118.116.4])
 by mail.server123.net (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Mon,  8 Feb 2016 17:51:25 +0100 (CET)
Received: from gatewagner.dyndns.org (77-57-36-72.dclient.hispeed.ch
 [77.57.36.72]) by v6.tansi.org (Postfix) with ESMTPA id C363320DC1FB
 for <dm-crypt@saout.de>; Mon,  8 Feb 2016 17:51:24 +0100 (CET)
Date: Mon, 8 Feb 2016 17:51:24 +0100
From: Arno Wagner <arno@wagner.name>
Message-ID: <20160208165124.GD5543@tansi.org>
References: <56B5356B.3030704@whgl.uni-frankfurt.de>
 <20160206025854.GA5986@tansi.org>
 <56B56605.4030907@whgl.uni-frankfurt.de>
 <20160207070958.35502402ED@darkstar.media.mit.edu>
 <20160207231750.GB29215@tansi.org>
 <20160208020631.E16BA402ED@darkstar.media.mit.edu>
 <56B80183.60006@whgl.uni-frankfurt.de>
 <20160208034324.790B2402ED@darkstar.media.mit.edu>
 <56B81A4E.9090909@whgl.uni-frankfurt.de>
 <20160208060924.9CCC5402ED@darkstar.media.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160208060924.9CCC5402ED@darkstar.media.mit.edu>
Subject: Re: [dm-crypt] The future of disk encryption with LUKS2
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On Mon, Feb 08, 2016 at 07:09:24 CET, f-dm-c@media.mit.edu wrote:
[...]

> [For example, and to take into account "OMG but what if massive giant
> corruptions and/or mislayered tables at start," have these as defaults:
> (a) FS < 10 meg --> no extra header
> (b) 10 meg < FS < 100 meg --> extra header after 1 meg gap
> (c) 100 meg < FS < 10 gig --> extra header after 10 meg gap
> (d) fs > 10 gig --> extra header after 100 meg gap

That strikes me as an exceedingly bad idea as it will be 
unpredictable to those users that need it. And I do not like
different places for md-RAID 1.x format superblocks one bit.
We should pick one thing, make it otional (but on by default)
and stick with it, so users do know where it is, regardless 
of other parameters.

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