All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Blanke <felixblanke@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS - SSD trim
Date: Thu, 22 Apr 2010 22:12:37 +0200	[thread overview]
Message-ID: <20100422221237.477736d1@gmail.com> (raw)
In-Reply-To: <4BD00C01.7050603@aktivix.org>

Hi,

first of all thank you guys a lot for helping me! 

I hope it is ok if I write one more question about those things:

I aligned the partition (which was allready fine) and the luks part to
the same value.

scooter ~ # fdisk -l /dev/sdb

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
224 heads, 56 sectors/track, 24918 cylinders
Units = cylinders of 12544 * 512 = 6422528 bytes
Disk identifier: 0x5328d0af

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          34      213220   83  Linux
/dev/sdb2              35         704     4202240   82  Linux swap /
   Solaris /dev/sdb3             705       13244    78650880   83  Linux
/dev/sdb4           13245       24918    73219328   83  Linux

scooter ~ # cryptsetup luksDump /dev/sdb4
...
Payload offset: 12544
...

The filesystem on top is btrfs. I didn't find any information about the
align thing and btrfs. I dont know mutch about align and those stuff :/


The problem is:

scooter ~ # hdparm -tT /dev/sdb3

/dev/sdb3:
 Timing cached reads:   18686 MB in  2.00 seconds = 9354.32 MB/sec
 Timing buffered disk reads:  758 MB in  3.00 seconds = 252.61 MB/sec

scooter ~ # hdparm -tT /dev/mapper/ssd 

/dev/mapper/ssd:
 Timing cached reads:   17432 MB in  2.00 seconds = 8725.18 MB/sec
 Timing buffered disk reads:  158 MB in  3.02 seconds =  52.36 MB/sec


The first value is perfect, then second one really sucks.
Obv. /dev/mapper/ssd is the decrypted /dev/sdb3

Any idea about that?


Regards,
Felix




Am Thu, 22 Apr 2010 09:42:41 +0100
schrieb mark <mark@aktivix.org>:

> -----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-----
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

  parent reply	other threads:[~2010-04-22 20:19 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
2010-04-22 20:12         ` Felix Blanke [this message]
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=20100422221237.477736d1@gmail.com \
    --to=felixblanke@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.