From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: SSD format/mount parameters questions
Date: Thu, 17 May 2012 15:45:27 +0100 [thread overview]
Message-ID: <jp32u7$vlc$1@dough.gmane.org> (raw)
For using SSDs:
Are there any format/mount parameters that should be set for using btrfs
on SSDs (other than the "ssd" mount option)?
General questions:
How long is the 'delay' for the delayed alloc?
Are file allocations aligned to 4kiB boundaries, or larger?
What byte value is used to pad unused space?
(Aside: For some, the erased state reads all 0x00, and for others the
erased state reads all 0xff.)
Background:
I've got a mix of various 120/128GB SSDs to newly set up. I will be
using ext4 on the critical ones, but also wish to compare with btrfs...
The mix includes some SSDs with the Sandforce controller that implements
its own data compression and data deduplication. How well does btrfs fit
with those compared to other non-data-compression controllers?
Regards,
Martin
next reply other threads:[~2012-05-17 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 14:45 Martin [this message]
2012-05-18 7:02 ` SSD format/mount parameters questions Sander
2012-05-18 15:08 ` Clemens Eisserer
2012-05-18 15:32 ` Tomasz Torcz
2012-05-18 16:09 ` Calvin Walton
2012-05-19 17:36 ` Martin Steigerwald
2012-05-22 21:30 ` Martin
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='jp32u7$vlc$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).