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>; Thu, 22 Apr 2010 11:37:10 +0200 (CEST)
Received: from int-mx08.intmail.prod.int.phx2.redhat.com
	(int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o3M9b8lD026240
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <dm-crypt@saout.de>; Thu, 22 Apr 2010 05:37:08 -0400
Received: from [10.36.9.44] (vpn2-9-44.ams2.redhat.com [10.36.9.44])
	by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
	id o3M9b7rZ003917
	for <dm-crypt@saout.de>; Thu, 22 Apr 2010 05:37:07 -0400
Message-ID: <4BD018C3.5040401@redhat.com>
Date: Thu, 22 Apr 2010 11:37:07 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <20100422004842.5eb40c0a@gmail.com>	<4BCF8371.60306@redhat.com>	<20100422010328.05990873@gmail.com>	<20100422021752.GA7060@tansi.org>
	<4BD00C01.7050603@aktivix.org>
In-Reply-To: <4BD00C01.7050603@aktivix.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] LUKS - SSD trim
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>
Cc: dm-crypt@saout.de

On 04/22/2010 10:42 AM, mark wrote:
> On 22/04/10 03:17, Arno Wagner wrote:
>> You can image it to a file on a conventional disk and
>> image it back, e.g. wioth dd_rescue. That should
>> also fix things, at least for a while.
> 
> I guess it might help to check that your partitions are aligned to the
> erase blocks on the SSD, before you restore the image of your brtfs.
> Look here http://www.saout.de/pipermail/dm-crypt/2010-February/000584.html

FYI: upstream svn have already automatic alignment code
(requires kernel 2.6.33 and above - topology ioclt calls supported).

I need just test it that it uses proper offset claculation:-),
but should be in cryptsetup 1.1.1

Anyway, yes - for SSD is VERY important to align the whole device stack
(partition, LUKS, LVM2, ...).
More important than TRIM support.

Milan