All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Marc Grondin <marcfgrondin@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Confusing output from fi us/df
Date: Tue, 21 Jun 2016 02:25:20 +0200	[thread overview]
Message-ID: <4c73e55f-aabb-4ec3-c419-e970b9506d7d@mendix.com> (raw)
In-Reply-To: <29fb52eb-9aed-5d12-1631-0a8d776fb69c@gmail.com>

Hi,

On 06/21/2016 01:30 AM, Marc Grondin wrote:
>
> I have a btrfs filesystem ontop of a 4x1tb mdraid raid5 array and I've
> been getting confusing output on metadata usage. Seems that even tho
> both data and metadata are in single profile metadata is reporting
> double the space(as if it was in dupe profile)

I guess that's a coincidence.

 From the total amount of space you have (on top of the mdraid), there's 
3 GiB allocated/reserved for use as metadata. Inside that 3 GiB, 1.53GiB 
of actual metadata is present.

>[...]
> Metadata,single: Size:3.00GiB, Used:1.53GiB
> /dev/mapper/storage2 3.00GiB

> Metadata, single: total=3.00GiB, used=1.53GiB

If you'd change to DUP, it would look like:

for fi usage:

Metadata,single: Size:3.00GiB, Used:1.53GiB
/dev/mapper/storage2 6.00GiB

for fi df:

Metadata, single: total=3.00GiB, used=1.53GiB

Except for the 6.00GiB which would show the actual usage on disk, the 
other metadata numbers all hide the profile ratio.

Hans

  reply	other threads:[~2016-06-21  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 23:30 Confusing output from fi us/df Marc Grondin
2016-06-21  0:25 ` Hans van Kranenburg [this message]
2016-06-21  9:40   ` Duncan
2016-06-21  0:55 ` Satoru Takeuchi
2016-06-22 18:52 ` Chris Murphy

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=4c73e55f-aabb-4ec3-c419-e970b9506d7d@mendix.com \
    --to=hans.van.kranenburg@mendix.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marcfgrondin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.