public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: jim owens <jowens@hp.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Metadata Duplication on a Single Disk Btrfs Setup
Date: Tue, 12 Jan 2010 13:27:52 -0500	[thread overview]
Message-ID: <4B4CBF28.6010602@hp.com> (raw)
In-Reply-To: <26a1f7961001121008u2d55eacobf2efd7a8ad39c7c@mail.gmail.com>

Mitch Harder wrote:
> On a single disk btrfs setup, such as for a desktop computer, what are
> the implecations of creating your btrfs partition with '-m single'?
> 
> At first, I assumed I would want a single disk desktop setup to be
> configured as 'single'.  But that may not be the case for metadata.
> 
> I see that the default is for metadata duplication in a single disk scenario.
> 
> Is duplication of the metadata important for recovery from common
> desktop user problems such as power interruption?

Duplication of metadata protects against unreadable disk blocks
or disk blocks that have garbage written in them. Power interruption
can cause that in rare cases (and on some hardware not so rare).

The more usual power loss issue is incomplete or stale data.  Even
single metadata mode should protect from that.

So the short answer is it provides some additional protection
at the expense of more space used.  How much you need that extra
protection depends on your hardware, power reliability, and how
valuable your data is.

jim

  reply	other threads:[~2010-01-12 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 18:08 Metadata Duplication on a Single Disk Btrfs Setup Mitch Harder
2010-01-12 18:27 ` jim owens [this message]
2010-01-13 22:17   ` Mitch Harder

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=4B4CBF28.6010602@hp.com \
    --to=jowens@hp.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mitch.harder@sabayonlinux.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