public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: linux-btrfs@vger.kernel.org
Subject: Metadata Duplication on a Single Disk Btrfs Setup
Date: Tue, 12 Jan 2010 12:08:19 -0600	[thread overview]
Message-ID: <26a1f7961001121008u2d55eacobf2efd7a8ad39c7c@mail.gmail.com> (raw)

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?

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 18:08 Mitch Harder [this message]
2010-01-12 18:27 ` Metadata Duplication on a Single Disk Btrfs Setup jim owens
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=26a1f7961001121008u2d55eacobf2efd7a8ad39c7c@mail.gmail.com \
    --to=mitch.harder@sabayonlinux.org \
    --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