public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Recover on SSD
Date: Mon, 6 May 2013 20:36:33 +0200	[thread overview]
Message-ID: <20130506183632.GA11132@BIFROST.fritz.box> (raw)
In-Reply-To: <5187E99C.2030105@googlemail.com>

[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]

On Mon, May 06, 2013 at 07:34:20PM +0200, Volker Armin Hemmann wrote:
> emm - no. Wear leveling does not need any spare blocks. A lot of drives
> do have spare blocks, but those are never the same size of the original
> size (at least not on drives you can buy for a sensible amount of
> money).  More like 120+8 or 160+16 or 256+16.
> 
> The spare blocks are used like on a hdd: some block goes bad, another
> one is mapped in.
> 
> Since the sdd firmware does not know if something was deleted or not* -
> it does know shit about filesystems**, you can of course dd an image, if
> you want to. Just like on a hdd.
> 
> *there are drives that do garbage collection without TRIM for fat and or
> ntfs.. so they seem to know a bit about filesystems.
> 
> ** and this is why TRIM exists in the first place. To tell the drive:
> yes, this data is gone. You don't need to care about it anymore.


The actual numbers were made up to make the point (maybe I should have
stated that in my OP). According to [1] they are normally between 7% -
37%.
Linux supports TRIM since Kernel 2.6.28. It's supported for several
filesystems (Ext4, Btrfs, FAT, GFS2 and XFS) but must be enabled via the
discard mount option. I don't have definitive information for Windows
but it seems to be supported by at least Windows 7 (as far as I can tell
without any user interaction).
Since the "deletion" happened under Windows I made a guess that it is
not totally unreasonable that dd may not work (if the deleted data would
have been "TRIMed").



[1] http://www.lsi.com/downloads/Public/Flash%20Storage%20Processors/LSI_PRS_FMS2012_TE21_Smith.pdf

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-05-06 18:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05 14:44 [gentoo-user] Recover on SSD Randolph Maaßen
2013-05-05 16:11 ` Alan McKinnon
2013-05-05 16:11 ` Volker Armin Hemmann
2013-05-05 16:16 ` Hinnerk van Bruinehsen
2013-05-05 19:36   ` Randolph Maaßen
2013-05-06  0:49     ` Randolph Maaßen
2013-05-06  4:50       ` Dale
2013-05-06 15:18       ` Paul Hartman
2013-05-06  6:50   ` Stroller
2013-05-06 11:00     ` Hinnerk van Bruinehsen
2013-05-06 17:34       ` Volker Armin Hemmann
2013-05-06 18:36         ` Hinnerk van Bruinehsen [this message]
2013-05-06 18:57           ` Alan McKinnon
2013-05-06 20:07             ` Randolph Maaßen
2013-05-07 14:49               ` Stroller
2013-05-07 14:56                 ` Alan McKinnon
2013-05-07 14:57                 ` Michael Mol
     [not found] <l68qd-4Mf-7@gated-at.bofh.it>
     [not found] ` <l69Pj-6Bu-11@gated-at.bofh.it>
     [not found]   ` <l6cWR-1TQ-13@gated-at.bofh.it>
     [not found]     ` <l6hWy-84A-11@gated-at.bofh.it>
     [not found]       ` <l6lGN-4fF-1@gated-at.bofh.it>
2013-05-06  5:16         ` Gregory Shearman
2013-05-06  5:29           ` Dale

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=20130506183632.GA11132@BIFROST.fritz.box \
    --to=h.v.bruinehsen@fu-berlin.de \
    --cc=gentoo-user@lists.gentoo.org \
    /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