linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: linux-btrfs@vger.kernel.org
Subject: Chunk map/control
Date: Wed, 22 Sep 2010 16:12:13 -0400	[thread overview]
Message-ID: <4C9A631D.2030202@cfl.rr.com> (raw)

Is there currently a way to view and manipulate the chunks?  If I
understand things correctly, a new fs has a few chunks:

1)  System chunk.  Contains tree of trees, device tree, chunk tree.
2)  Metadata chunk.  Contains the directory tree for the default subvol,
and any additional subvols/snapshots you create.  Directory entries and
inodes are in this tree.
3)  Data chunk.  Files with significant data have blocks allocated from
this chunk.

The system chunk is always mirrored, even on a single disk.  The
metadata chunk is mirrored by default, but can be changed with a
parameter to mkfs.  The data chunk is striped by default, but can be
changed via parameter to mkfs.  The chunks are all expanded as needed.
Is this correct, and is there a way to create a subvol with a new pair
of metadata/data chunks and specify how they should be striped or
mirrored across what devices?

             reply	other threads:[~2010-09-22 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 20:12 Phillip Susi [this message]
2010-11-10 15:08 ` Chunk map/control Phillip Susi

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=4C9A631D.2030202@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --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;
as well as URLs for NNTP newsgroup(s).