linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Chester <somethingsome2000@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: efficiency of btrfs cow
Date: Wed, 23 Mar 2011 12:19:39 -0400	[thread overview]
Message-ID: <4D8A1D9B.7060706@interlinx.bc.ca> (raw)
In-Reply-To: <AANLkTikF3e2X=UK2pJmNgaTAJqR0DXymKfzr=drhC5S=@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

On 11-03-23 11:53 AM, Chester wrote:
> I'm not a developer, but I think it goes something like this:
> btrfs doesn't write the filesystem on the entire device/partition at
> format time, rather, it dynamically increases the size of the
> filesystem as data is used. That's why formating a disk in btrfs can
> be so fast.

Indeed, this much is understood, which is why I am using btrfs fi df to
try to determine how much of the increase in raw device usage is the
dynamic allocation of metadata.

Cheers,
b.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-03-23 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06 15:46 efficiency of btrfs cow Brian J. Murrell
2011-03-06 16:02 ` Fajar A. Nugraha
2011-03-06 16:11   ` Brian J. Murrell
2011-03-06 16:17   ` Calvin Walton
2011-03-06 16:18     ` Brian J. Murrell
2011-03-06 17:22   ` Freddie Cash
2011-03-06 16:06 ` Calvin Walton
2011-03-06 16:17   ` Brian J. Murrell
2011-03-23 12:39   ` Brian J. Murrell
2011-03-23 15:53     ` Chester
2011-03-23 16:19       ` Brian J. Murrell [this message]
2011-03-23 17:36     ` Kolja Dummann

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=4D8A1D9B.7060706@interlinx.bc.ca \
    --to=brian@interlinx.bc.ca \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=somethingsome2000@gmail.com \
    /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).