From: Russell Coker <russell@coker.com.au>
To: Robert Krig <robert.krig@render-wahnsinn.de>
Cc: "linux-btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs raid1 metadata, single data
Date: Fri, 7 Aug 2015 19:18:02 +1000 [thread overview]
Message-ID: <201508071918.02231.russell@coker.com.au> (raw)
In-Reply-To: <55C47136.2080402@render-wahnsinn.de>
On Fri, 7 Aug 2015 06:49:58 PM Robert Krig wrote:
> What exactly is contained in btrfs metadata?
Much the same as in metadata for every other filesystem.
> I've read about some users setting up their btrfs volumes as
> data=single, but metadata=raid1
>
> Is there any actual benefit to that? I mean, if you keep your data as
> single, but have multiple copies of metadata, does that still allow you
> to recover from data corruption? Or is metadata redundancy a benefit to
> ensure that your btrfs volume remains mountable/readable?
If you have redundant metadata and experience corruption then you will know
the name of every file that has data corruption, this is really good for
restoring from backup. Also you will be protected against corruption of a
root directory causing massive data loss.
If you have the bad luck to have certain metadata structures corrupted with no
redundancy then you can face massive data loss and possibly have the entire
filesystem become at least temporarily unusable. While corruption of the root
directory is unlikely it is possible. With "dup" metadata I've seen a BTRFS
filesystem remain usable after 12,000+ read errors.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2015-08-07 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 8:49 btrfs raid1 metadata, single data Robert Krig
2015-08-07 9:18 ` Russell Coker [this message]
2015-08-07 9:47 ` Sjoerd
2015-08-07 10:40 ` Mike Fleetwood
2015-08-07 11:38 ` Austin S Hemmelgarn
2015-08-07 20:07 ` Sjoerd
2015-08-07 11:13 ` Duncan
2015-08-07 10:26 ` Duncan
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=201508071918.02231.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=robert.krig@render-wahnsinn.de \
/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