public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: AGs in btrfs
Date: Mon, 04 Aug 2008 08:45:36 -0400	[thread overview]
Message-ID: <1217853936.29139.39.camel@think.oraclecorp.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0808022018190.21001@fbirervta.pbzchgretzou.qr>

On Sat, 2008-08-02 at 20:20 -0400, Jan Engelhardt wrote:
> Hi,
> 
> 
> I was wondering whether btrfs has a concept similar to xfs's "allocation 
> groups", which, as far as I understand, means that the filesystem has 
> multiple B-tree roots to allow for more finegrained locking and desaster 
> containment (losing only 1/16th of the fs in a medium-worst case).

Yes and no, we'll eventually have multiple extent allocation trees that
provide some of what the AGs do.  Pulling out hte btree roots for more
fault tolerance is something we need to study.

-chris



      reply	other threads:[~2008-08-04 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03  0:20 AGs in btrfs Jan Engelhardt
2008-08-04 12:45 ` Chris Mason [this message]

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=1217853936.29139.39.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=jengelh@medozas.de \
    --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