From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: SSD erase state and reducing SSD wear
Date: Tue, 22 May 2012 22:47:42 +0100 [thread overview]
Message-ID: <jph1hu$2tq$1@dough.gmane.org> (raw)
I've got two recent examples of SSDs. Their pristine state from the
manufacturer shows:
Device Model: OCZ-VERTEX3
# hexdump -C /dev/sdd
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
1bf2976000
Device Model: OCZ VERTEX PLUS
(OCZ VERTEX 2E)
# hexdump -C /dev/sdd
00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
*
df99e6000
What's a good way to test what state they get erased to from a TRIM
operation?
Can btrfs detect the erase state and pad unused space in filesystem
writes with the same value so as to reduce SSD wear?
Regards,
Martin
next reply other threads:[~2012-05-22 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 21:47 Martin [this message]
2012-05-23 4:19 ` SSD erase state and reducing SSD wear Calvin Walton
2012-05-23 15:44 ` Martin
2012-05-23 19:50 ` Calvin Walton
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='jph1hu$2tq$1@dough.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--cc=linux-btrfs@vger.kernel.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).