From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from newyear.aktivix.org (newyear.aktivix.org [209.234.249.206]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Thu, 22 Apr 2010 10:42:51 +0200 (CEST) Message-ID: <4BD00C01.7050603@aktivix.org> Date: Thu, 22 Apr 2010 09:42:41 +0100 From: mark MIME-Version: 1.0 References: <20100422004842.5eb40c0a@gmail.com> <4BCF8371.60306@redhat.com> <20100422010328.05990873@gmail.com> <20100422021752.GA7060@tansi.org> In-Reply-To: <20100422021752.GA7060@tansi.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] LUKS - SSD trim List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 Cheers, Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvQDAEACgkQ3b8v4BN9hRRSrgCfWeLBY437QMYCSXHPQ0m89GQd MMQAn2kqFW6IFcEgQ3Ebo3kMmt4p/i9G =gQav -----END PGP SIGNATURE-----