From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRuWNRzl3Wu2 for ; Tue, 20 Sep 2011 17:21:50 +0200 (CEST) Received: from vserver3082.vserver-on.de (vserver3082.vserver-on.de [109.73.50.87]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 20 Sep 2011 17:21:50 +0200 (CEST) Received: from [10.0.0.3] (dslb-092-074-237-211.pools.arcor-ip.net [92.74.237.211]) by vserver3082.vserver-on.de (Postfix) with ESMTPSA id E54CA14E1C3 for ; Tue, 20 Sep 2011 17:21:49 +0200 (CEST) Message-ID: <4E78AF92.9040309@alexanderkoch.net> Date: Tue, 20 Sep 2011 17:21:54 +0200 From: Alexander Koch MIME-Version: 1.0 References: <1316515022.7965.31.camel@zarniwoop> <20110920114724.GA21251@tansi.org> In-Reply-To: <20110920114724.GA21251@tansi.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] (More) Questions about LUKS / LVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Am 20.09.2011 13:47, schrieb Arno Wagner: > With an SSD, things are a bit different. Due to the large > internal sector size, the header can be in a sector that > also has data that gets rewritten in it. As sectors are > always written completely, the header then is at risk whenever > that data gets rewritten. Did I get that right: by using the TRIM-support available with kernel 3.1 I risk loosing my LUKS headers at regular use?? No chance to align the payload (data) in such a way that it starts at a new sector, which then can be TRIMed without loosing the header? Thanks, Alex