From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Mon, 24 Aug 2009 17:55:41 +0200 (CEST)
Message-ID: <4A92B7F9.7060102@redhat.com>
Date: Mon, 24 Aug 2009 17:55:37 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <20090824100211.5c162f1a@Computername>
In-Reply-To: <20090824100211.5c162f1a@Computername>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Broken header of a luks-partition - more than once
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: spamzad@googlemail.com
Cc: dm-crypt@saout.de

spamzad@googlemail.com wrote:
> Something must have overwritten the header (posted it at the bottom) -
> and I have no clue what.
> That's exactly my question now: might it be a bug in cryptsetup or can
> i rule that out?

Cryptsetup never write empty first sectors except explicit LUKS format.
(Of course this can very rarely happen if hw/driver problem appears...)

But see crypttab here - you have tmp device created as regular encrypted device
with random key - are you sure that kernel _cannot_ swap sda & sdb and
your system just formats temp device here?

> # <target name> <source device>         <key file>      <options>
> home            /dev/sdb2               none            luks
> ctmp            /dev/sda2               /dev/urandom
> tmp,cipher=aes-cbc-essiv:sha256
> cswap           /dev/sda5               /dev/urandom
> swap,cipher=aes-cbc-essiv:sha256

Milan
--
mbroz@redhat.com