From: Marc MERLIN <marc@merlins.org>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Using BTRFS on SSD now ?
Date: Thu, 5 Jun 2014 07:56:32 -0700 [thread overview]
Message-ID: <20140605145632.GD14713@merlins.org> (raw)
In-Reply-To: <2215647.hErg5R77lo@zafu>
On Thu, Jun 05, 2014 at 03:30:26PM +0200, Swâmi Petaramesh wrote:
> Hi,
>
> I just received a new laptop with a Micron 256GB SSD, and I plan to install
> Fedora 20 onto it.
>
> I'm considering either BTRFS or ext4 (over LUKS-encrypted LVM) for this
> machine, but I'm afraid BTRFS might generate too much writes and shorten the
> SSD lifespan... Or am I mistaken ?
Yeah,
1) a lot of us use btrfs on SSDs
2) SSD write lifetime is more than you think
However SSDs, especially at least earlier models of the one you got, still
randomly die, and take your data with them. It's not because of number of
writes, but bad firmware and/or a single chip that dies and isn't redundant on
some drives.
> Is there any pro/cons currently, on a 3.14 kernel, about using BTRFS along
> with an SSD ?
It's not foolproof, but works well enough for many. Have backups, but
because of your SSD, you should definitely have backups anyway.
> Is there specific advice about leaf size, use of compression, snapshots,
> (auto-)defrag etc, that might be relevant especially for SSDs ?
compression: lzo, not zlib (zlib will slow down your SSD)
snapshots:
http://marc.merlins.org/perso/btrfs/2014-03.html#Btrfs-Tips_-How-To-Setup-Netapp-Style-Snapshots
auto-defrag: not really (read the archives)
other options: leave default
add -o discard to mount options
Do not use LVM, it's totally unnecessary and will slow you down. Dmcrypt is
ok, however add discard to cryptsetup options too:
root2 /dev/sda2 /pwd luks,discard
legolas:~# grep discard /proc/cmdline
root=/dev/mapper/cryptroot ro rootflags=subvol=root cryptopts=source=/dev/sda4,keyscript=/sbin/cryptgetpw,discard
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2014-06-05 14:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 13:30 Using BTRFS on SSD now ? Swâmi Petaramesh
2014-06-05 14:42 ` Russell Coker
2014-06-05 15:14 ` Swâmi Petaramesh
2014-06-05 16:26 ` Marc MERLIN
2014-06-05 18:34 ` Chris Murphy
2014-06-05 14:56 ` Marc MERLIN [this message]
2014-06-05 15:11 ` Roman Mamedov
2014-06-08 14:26 ` Pavel Volkov
2014-06-05 15:59 ` Christoph Anton Mitterer
2014-06-05 17:07 ` Swâmi Petaramesh
2014-06-05 18:13 ` Chris Murphy
2014-06-05 19:05 ` Marc MERLIN
2014-06-05 22:25 ` Duncan
2014-06-05 23:58 ` Martin K. Petersen
2014-06-06 0:24 ` Chris Murphy
2014-06-06 0:35 ` Duncan
2014-06-08 14:48 ` Pavel Volkov
2014-06-08 16:51 ` Martin K. Petersen
2014-06-05 21:15 ` Duncan
2014-06-05 16:17 ` Martin Steigerwald
2014-06-05 18:00 ` Chris Murphy
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=20140605145632.GD14713@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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).