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 ; Sat, 6 Feb 2010 00:48:23 +0100 (CET) Message-ID: <4B6CAE3F.2060605@aktivix.org> Date: Fri, 05 Feb 2010 23:48:15 +0000 From: mark MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig94B603CFE30C6075C6F4D7CC" Subject: [dm-crypt] How to optimise encrypted filesystems on an SSD? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig94B603CFE30C6075C6F4D7CC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi there. For a while I've been using LUKS/dm-crypt with LVM2 to secure hard drives in laptops and servers. Recently I've moved one of my filesystems onto a solid-state drive (Intel X25-M-G2 80GB with latest firmware). There are some excellent instructions here http://thunk.org/tytso/blog/2009/02/20/aligning-filesystems-to-an-ssds-er= ase-block-size/ on how to align ext4 and LVM to the erase block size of the SSD. However I've not been able to find a recipe for optimising an encrypted filesystem in the same way. A typical usage case for me would be this, from following defaults for encrypted lvm on the Debian installer: /dev/sda1 79GB crypt-luks /dev/mapper/sda1_crypt holds PV for LVM2 PV has a VG with two LVs, 4GB swap and the rest for ext4 / /dev/sda5 256MB ext2 /boot Could anyone explain how I might go about aligning/optimising this, or point me to some instructions? Am I better putting lvm over luks or luks over lvm? Or something entirely different? Thanks in advance, Mark --------------enig94B603CFE30C6075C6F4D7CC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktsrj8ACgkQ3b8v4BN9hRSi0gCeMnKwgvQRn9bWmeZy0rt92w2a Xk0AoOzHx/6RvQfsJrQuHZqyHcMreY7M =BMTp -----END PGP SIGNATURE----- --------------enig94B603CFE30C6075C6F4D7CC--