From: Hendrik Friedel <hendrik@friedels.name>
To: Hugo Mills <hugo@carfax.org.uk>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: understanding btrfs fi df
Date: Sat, 22 Aug 2015 00:45:34 +0200 [thread overview]
Message-ID: <55D7AA0E.1060506@friedels.name> (raw)
In-Reply-To: <55D4BEF2.4040107@friedels.name>
Hello Hugo,
>> It shouldn't happen, as I understand how the process works. Can you
>> show the output of "btrfs fi df /mnt/__Complete_Disk"? Let's just
>> check that everything is indeed RAID-5 still.
>
> Here we go:
>
> btrfs fi df /mnt/__Complete_Disk
>
> Data, RAID5: total=3.79TiB, used=3.78TiB
> System, RAID5: total=32.00MiB, used=416.00KiB
> Metadata, RAID5: total=6.46GiB, used=4.85GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
can you help me on this? As far as I see, it's all Raid5.
So,
>> After this, we're probably going to have to look at the device and
>> chunk trees to work out what's going on.
Can you help me on this?
Regards,
Hendrik
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
prev parent reply other threads:[~2015-08-21 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 14:33 understanding btrfs fi df Hendrik Friedel
2015-08-16 14:57 ` Hugo Mills
2015-08-19 16:10 ` Hendrik Friedel
2015-08-19 16:17 ` Hugo Mills
2015-08-19 17:37 ` Hendrik Friedel
2015-08-21 22:45 ` Hendrik Friedel [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=55D7AA0E.1060506@friedels.name \
--to=hendrik@friedels.name \
--cc=hugo@carfax.org.uk \
--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).