From: Milan Broz <mbroz@redhat.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS - SSD trim
Date: Thu, 22 Apr 2010 11:37:07 +0200 [thread overview]
Message-ID: <4BD018C3.5040401@redhat.com> (raw)
In-Reply-To: <4BD00C01.7050603@aktivix.org>
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
next prev parent reply other threads:[~2010-04-22 9:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 22:48 [dm-crypt] LUKS - SSD trim Felix Blanke
2010-04-21 23:00 ` Milan Broz
2010-04-21 23:03 ` Felix Blanke
2010-04-22 2:17 ` Arno Wagner
2010-04-22 8:42 ` mark
2010-04-22 9:37 ` Milan Broz [this message]
2010-04-22 20:12 ` Felix Blanke
2010-04-22 22:20 ` Richard Zidlicky
2010-04-22 22:22 ` Richard Zidlicky
2010-04-23 8:49 ` Milan Broz
2010-04-23 10:20 ` Mikko Rauhala
2010-04-23 11:13 ` Richard Zidlicky
2010-04-23 11:46 ` Milan Broz
2010-04-23 20:09 ` Richard Zidlicky
2010-04-23 20:45 ` Milan Broz
2010-04-23 22:59 ` Richard Zidlicky
2010-04-24 15:59 ` Arno Wagner
2010-04-24 16:44 ` Richard Zidlicky
2010-04-24 17:01 ` Arno Wagner
2010-04-22 6:17 ` Heinz Diehl
2010-05-14 7:35 ` JG
-- strict thread matches above, loose matches on Subject: below --
2010-05-27 13:14 Christoph Anton Mitterer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD018C3.5040401@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox