From: One Thousand Gnomes <gnomes-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
To: Peter Wu <peter-VTkQYDcBqhK7DlmcbJSQ7g@public.gmane.org>
Cc: Tim Small <tim-v0yPK6tSSg/10XsdtD+oqA@public.gmane.org>,
linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: blkdiscard vs hdparm for erasing a SSD?
Date: Tue, 21 Oct 2014 18:06:07 +0100 [thread overview]
Message-ID: <20141021180607.6f2ee53d@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <1471878.ajvL24Q1JG@al>
> The names suggest that TRIM is for marking sectors for garbage collection while
> SECURITY ERASE tries a bit harder. From the runtime performance point of view, I
> would expect that S.E. is at least as fast as TRIM as no more garbage needs to
> be collected at a later point. From a durability PoV, not so sure, it could be
> that S.E. overwrites all blocks (or not).
>
> Anyway, I have not read into the details and unless the standards (and
> manufacturers) can guarantee certain behavior, it will likely vary between
> device models.
On a decent SSD security erase is almost immediate and does not need to
overwrite anything.
Alan
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-21 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 13:12 blkdiscard vs hdparm for erasing a SSD? Peter Wu
2014-10-15 14:21 ` Tim Small
[not found] ` <543E82DE.8070405-v0yPK6tSSg/10XsdtD+oqA@public.gmane.org>
2014-10-16 10:17 ` Peter Wu
2014-10-21 17:06 ` One Thousand Gnomes [this message]
2014-10-28 2:09 ` Mark Lord
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=20141021180607.6f2ee53d@alan.etchedpixels.co.uk \
--to=gnomes-qbu/x9rampvanceybjwyrvxrex20p6io@public.gmane.org \
--cc=linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=peter-VTkQYDcBqhK7DlmcbJSQ7g@public.gmane.org \
--cc=tim-v0yPK6tSSg/10XsdtD+oqA@public.gmane.org \
--cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).