From: Hugo Mills <hugo@carfax.org.uk>
To: Tomasz Chmielewski <tch@virtall.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs progs release 3.18
Date: Tue, 30 Dec 2014 21:44:17 +0000 [thread overview]
Message-ID: <20141230214417.GC26040@carfax.org.uk> (raw)
In-Reply-To: <09d8530e73aed4552f1b3a6297c20360@admin.virtall.com>
[-- Attachment #1: Type: text/plain, Size: 2663 bytes --]
On Tue, Dec 30, 2014 at 10:38:38PM +0100, Tomasz Chmielewski wrote:
> >* filesystem usage - give an overview of fs usage in a way (道,
> >みち, michi) that's more
> >* device usage - more detailed information about per-device allocations
> > * same restrictions as for 'fi usage'
>
> Interesting.
>
> Used these to create a filesystem, with btrfs-progs v3.17.3:
>
> # mkfs.btrfs -O skinny-metadata -d raid1 -m raid1 /dev/sda4 /dev/sdb4 -f
>
>
> Now, with btrfs-progs 3.18 and these new options I can see that the
> fs is partially single, not RAID-1 - how come?
It's always been like that with a new FS. The small single chunks
are part of the way that mkfs works, and will go away on the first
balance operation. It's harmless, and can safely be ignored.
Hugo.
> # btrfs fil us /srv
> Overall:
> Device size: 5.25TiB
> Device allocated: 510.04GiB
> Device unallocated: 4.76TiB
> Used: 505.39GiB
> Free (estimated): 2.38TiB (min: 2.38TiB)
> Data ratio: 2.00
> Metadata ratio: 2.00
> Global reserve: 512.00MiB (used: 0.00B)
>
> Data,single: Size:8.00MiB, Used:0.00B
> /dev/sda4 8.00MiB
>
> Data,RAID1: Size:252.00GiB, Used:250.56GiB
> /dev/sda4 252.00GiB
> /dev/sdb4 252.00GiB
>
> Metadata,single: Size:8.00MiB, Used:0.00B
> /dev/sda4 8.00MiB
>
> Metadata,RAID1: Size:3.00GiB, Used:2.13GiB
> /dev/sda4 3.00GiB
> /dev/sdb4 3.00GiB
>
> System,single: Size:4.00MiB, Used:0.00B
> /dev/sda4 4.00MiB
>
> System,RAID1: Size:8.00MiB, Used:64.00KiB
> /dev/sda4 8.00MiB
> /dev/sdb4 8.00MiB
>
> Unallocated:
> /dev/sda4 2.38TiB
> /dev/sdb4 2.38TiB
>
>
> root@backup01 ~ # btrfs dev us /srv
> /dev/sda4, ID: 1
> Device size: 2.63TiB
> Data,single: 8.00MiB
> Data,RAID1: 252.00GiB
> Metadata,single: 8.00MiB
> Metadata,RAID1: 3.00GiB
> System,single: 4.00MiB
> System,RAID1: 8.00MiB
> Unallocated: 2.38TiB
>
> /dev/sdb4, ID: 2
> Device size: 2.63TiB
> Data,RAID1: 252.00GiB
> Metadata,RAID1: 3.00GiB
> System,RAID1: 8.00MiB
> Unallocated: 2.38TiB
>
>
--
Hugo Mills | The trouble with you, Ibid, is you think you know
hugo@... carfax.org.uk | everything.
http://carfax.org.uk/ |
PGP: 65E74AC0 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-12-30 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 21:38 Btrfs progs release 3.18 Tomasz Chmielewski
2014-12-30 21:44 ` Hugo Mills [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-30 16:34 David Sterba
2014-12-30 17:25 ` Martin Steigerwald
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=20141230214417.GC26040@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=tch@virtall.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).