From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: checksum error in metadata node - best way to move root fs to new drive?
Date: Thu, 11 Aug 2016 04:50:53 +0000 (UTC) [thread overview]
Message-ID: <pan$631e4$8ace778e$d2bf1967$d5b4e8cc@cox.net> (raw)
In-Reply-To: CAGdWbB72DLAkV3EwO-7Sakc4gPHRT=GmU5ftxo0YfR0wjBefNQ@mail.gmail.com
Dave T posted on Wed, 10 Aug 2016 18:01:44 -0400 as excerpted:
> Does anyone have any thoughts about using dup mode for metadata on a
> Samsung 950 Pro (or any NVMe drive)?
The biggest problem with dup on ssds is that some ssds (particularly the
ones with the sandforce controllers) do dedup, so you'd be having btrfs
do dup while the filesystem dedups, to no effect except more cpu and
device processing!
(The other argument for single on ssd that I've seen is that because the
FTL ultimately places the data, and because both copies are written at
the same time, there's a good chance that the FTL will write them into
the same erase block and area, and a defect in one will likely be a
defect in the other as well. That may or may not be, I'm not qualified
to say, but as explained below, I do choose to take my chances on that
and thus do run dup on ssd.)
So as long as the SSD doesn't have a deduping FTL, I'd suggest dup for
metadata on ssd does make sense. Data... not so sure on, but certainly
metadata, because one bad block of metadata can be many messed up files.
On my ssds here, which I know don't do dedup, most of my btrfs are raid1
on the pair of ssds. However, /boot is different since I can't really
point grub at two different /boots, so I have my working /boot on one
device, with the backup /boot on the other, and the grub on each one
pointed at its respective /boot, so I can select working or backup /boot
from the BIOS and it'll just work. Since /boot is so small, it's mixed-
mode chunks, meaning data and metadata are mixed together and the
redundancy mode applies to both at once instead of each separately. And
I chose dup, so it's dup for both data and metadata.
Works fine, dup for both data and metadata on non-deduping ssds, but of
course that means data takes double the space since there's two copies of
it, and that gets kind of expensive on ssd, if it's more than the
fraction of a GiB that's /boot.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-08-11 4:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 3:27 checksum error in metadata node - best way to move root fs to new drive? Dave T
2016-08-10 6:27 ` Duncan
2016-08-10 19:46 ` Austin S. Hemmelgarn
2016-08-10 21:21 ` Chris Murphy
2016-08-10 22:01 ` Dave T
2016-08-10 22:23 ` Chris Murphy
2016-08-10 22:52 ` Dave T
2016-08-11 14:12 ` Nicholas D Steeves
2016-08-11 14:45 ` Austin S. Hemmelgarn
2016-08-11 19:07 ` Duncan
2016-08-11 20:43 ` Chris Murphy
2016-08-12 3:11 ` Duncan
2016-08-12 3:51 ` Chris Murphy
2016-08-11 20:33 ` Chris Murphy
2016-08-11 7:18 ` Andrei Borzenkov
2016-08-11 4:50 ` Duncan [this message]
2016-08-11 5:06 ` Gareth Pye
2016-08-11 8:20 ` Duncan
2016-08-12 17:00 ` Patrik Lundquist
2016-08-10 21:15 ` Chris Murphy
2016-08-10 22:50 ` Dave T
-- strict thread matches above, loose matches on Subject: below --
2016-08-11 20:23 Dave T
2016-08-12 4:13 ` Duncan
2016-08-12 8:14 ` Adam Borowski
2016-08-12 12:04 ` Austin S. Hemmelgarn
2016-08-12 15:06 ` Duncan
2016-08-15 11:33 ` Austin S. Hemmelgarn
2016-08-12 17:02 ` 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='pan$631e4$8ace778e$d2bf1967$d5b4e8cc@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.