Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hendrik Friedel <hendrik@friedels.name>
To: Chris Murphy <lists@colorremedies.com>,
	Hugo Mills <hugo@carfax.org.uk>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Data single *and* raid?
Date: Sun, 02 Aug 2015 14:54:40 +0200	[thread overview]
Message-ID: <55BE1310.20608@friedels.name> (raw)
In-Reply-To: <CAJCQCtTY0bWrFmm_6An9QcPm7ek53vCrFHjZjehHf-UotXJ7+A@mail.gmail.com>

Hello,

>>     Looking at the btrfs fi show output, you've probably run out of
>> space during the conversion, probably due to an uneven distribution of
>> the original "single" chunks.
>>
>>     I think I would suggest balancing the single chunks, and trying the
>> conversion (of the unconverted parts) again:
>>
>> # btrfs balance start -dprofiles=single -mprofile=raid1 /mnt/new_storage/
>> # btrfs balance start -dconvert=raid5,soft -mconvert=raid5,soft /mnt/new_storage/
>>
>
> Yep I bet that's it also. btrfs fi usage might be better at exposing this case.


Thanks for your hints.
The balance is running now for about 11h:
The status is a bit surprising to me:
0 out of about 2619 chunks balanced (4165 considered), 100% left

btrfs fi usage is also surprising:
Overall:
     Device size:                   8.19TiB
     Device allocated:              2.56TiB
     Device unallocated:            5.62TiB
     Device missing:                  0.00B
     Used:                          2.56TiB
     Free (estimated):             11.65TiB      (min: 2.81TiB)
     Data ratio:                       0.48
     Metadata ratio:                   1.33
     Global reserve:              512.00MiB      (used: 0.00B)

Data,single: Size:2.55TiB, Used:2.55TiB
    /dev/sdc        1.60TiB
    /dev/sde      975.44GiB

Data,RAID5: Size:2.73TiB, Used:2.72TiB
    /dev/sdc        1.12TiB
    /dev/sdd        2.73TiB
    /dev/sde        1.61TiB

Metadata,RAID1: Size:6.00GiB, Used:5.33GiB
    /dev/sdc        5.00GiB
    /dev/sdd        1.00GiB
    /dev/sde        6.00GiB

Metadata,RAID5: Size:3.00GiB, Used:2.99GiB
    /dev/sdc        2.00GiB
    /dev/sdd        1.00GiB
    /dev/sde        3.00GiB

System,RAID5: Size:32.00MiB, Used:736.00KiB
    /dev/sdd       32.00MiB
    /dev/sde       32.00MiB

Unallocated:
    /dev/sdc        1.02MiB
    /dev/sdd        1.02MiB
    /dev/sde      164.59GiB


I hope, that is because Raid5 is not implemented yet?

Regards,
Hendrik

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


  parent reply	other threads:[~2015-08-02 12:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-01 20:09 Data single *and* raid? Hendrik Friedel
2015-08-01 20:24 ` Chris Murphy
2015-08-01 20:32 ` Hugo Mills
2015-08-01 20:44   ` Chris Murphy
2015-08-01 21:45     ` Duncan
2015-08-01 22:26       ` Chris Murphy
2015-08-01 22:34         ` Hugo Mills
2015-08-02  0:27           ` Duncan
2015-08-02  1:14             ` Chris Murphy
2015-08-02  3:46               ` Duncan
2015-08-02 18:31                 ` Chris Murphy
2015-08-02 19:06                   ` Hugo Mills
2015-08-02 12:54     ` Hendrik Friedel [this message]
2015-08-06 18:57     ` Hendrik Friedel
2015-08-07  1:26       ` Qu Wenruo
2015-08-07  5:16         ` Hendrik Friedel
2015-08-07  6:25           ` Duncan
2015-08-07  8:11           ` Hugo Mills

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=55BE1310.20608@friedels.name \
    --to=hendrik@friedels.name \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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