linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <bradtem@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: RAID-1 refuses to balance large drive
Date: Wed, 23 Mar 2016 12:01:20 +0800	[thread overview]
Message-ID: <56F21510.6050707@cn.fujitsu.com> (raw)
In-Reply-To: <56F1E7BE.1000004@gmail.com>



Brad Templeton wrote on 2016/03/22 17:47 -0700:
> I have a RAID 1, and was running a bit low, so replaced a 2TB drive with
> a 6TB.  The other drives are a 3TB and a 4TB.    After switching the
> drive, I did a balance and ... essentially nothing changed.  It did not
> balance clusters over to the 6TB drive off of the other 2 drives.  I
> found it odd, and wondered if it would do it as needed, but as time went
> on, the filesys got full for real.

Did you resized the replaced deivces to max?
Without resize, btrfs still consider it can only use 2T of the 6T devices.

Thanks,
Qu

>
> Making inquiries on the IRC channel, it was suggested perhaps the drives
> were too full for a balance, but they had at least 50gb free I would
> estimate, when I swapped.    As a test, I added a 4th drive, a spare
> 20gb partition and did a balance.  The balance did indeed balance the 3
> small drives, so they now each have 6gb unallocated, but the big drive
> remained unchanged.   The balance reported it operated on almost all the
> clusters, though.
>
> Linux kernel 4.2.0 (Ubuntu Wiley)
>
> Label: 'butter'  uuid: a91755d4-87d8-4acd-ae08-c11e7f1f5438
>          Total devices 4 FS bytes used 3.88TiB
>          devid    1 size 3.62TiB used 3.62TiB path /dev/sdi2
>          devid    2 size 2.73TiB used 2.72TiB path /dev/sdh
>          devid    3 size 5.43TiB used 1.42TiB path /dev/sdg2
>          devid    4 size 20.00GiB used 14.00GiB path /dev/sda1
>
> btrfs fi usage /local
>
> Overall:
>      Device size:                  11.81TiB
>      Device allocated:              7.77TiB
>      Device unallocated:            4.04TiB
>      Device missing:                  0.00B
>      Used:                          7.76TiB
>      Free (estimated):              2.02TiB      (min: 2.02TiB)
>      Data ratio:                       2.00
>      Metadata ratio:                   2.00
>      Global reserve:              512.00MiB      (used: 0.00B)
>
> Data,RAID1: Size:3.87TiB, Used:3.87TiB
>     /dev/sda1      14.00GiB
>     /dev/sdg2       1.41TiB
>     /dev/sdh        2.72TiB
>     /dev/sdi2       3.61TiB
>
> Metadata,RAID1: Size:11.00GiB, Used:9.79GiB
>     /dev/sdg2       5.00GiB
>     /dev/sdh        7.00GiB
>     /dev/sdi2      10.00GiB
>
> System,RAID1: Size:32.00MiB, Used:572.00KiB
>     /dev/sdg2      32.00MiB
>     /dev/sdi2      32.00MiB
>
> Unallocated:
>     /dev/sda1       6.00GiB
>     /dev/sdg2       4.02TiB
>     /dev/sdh        5.52GiB
>     /dev/sdi2       7.36GiB
>
> ----------------------
> btrfs fi df /local
> Data, RAID1: total=3.87TiB, used=3.87TiB
> System, RAID1: total=32.00MiB, used=572.00KiB
> Metadata, RAID1: total=11.00GiB, used=9.79GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
> I would have presumed that a balance would take blocks found on both the
> 3TB and 4TB, and move one of them over to the 6TB until all had 1.3TB of
> unallocated space.  But this does not happen.  Any clues on how to make
> it happen?
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>



  reply	other threads:[~2016-03-23  4:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23  0:47 RAID-1 refuses to balance large drive Brad Templeton
2016-03-23  4:01 ` Qu Wenruo [this message]
2016-03-23  4:47   ` Brad Templeton
2016-03-23  5:42     ` Chris Murphy
     [not found]       ` <56F22F80.501@gmail.com>
2016-03-23  6:17         ` Chris Murphy
2016-03-23 16:51           ` Brad Templeton
2016-03-23 18:34             ` Chris Murphy
2016-03-23 19:10               ` Brad Templeton
2016-03-23 19:27                 ` Alexander Fougner
2016-03-23 19:33                 ` Chris Murphy
2016-03-24  1:59                   ` Qu Wenruo
2016-03-24  2:13                     ` Brad Templeton
2016-03-24  2:33                       ` Qu Wenruo
2016-03-24  2:49                         ` Brad Templeton
2016-03-24  3:44                           ` Chris Murphy
2016-03-24  3:46                           ` Qu Wenruo
2016-03-24  6:11                           ` Duncan
2016-03-25 13:16                   ` Patrik Lundquist
2016-03-25 14:35                     ` Henk Slager
2016-03-26  4:15                       ` Duncan
     [not found]                       ` <CAHz9+Emc4DsXoMLKYrp1TfN+2r2cXxaJmPyTnpeCZF=h0FhtMg@mail.gmail.com>
2018-05-27  1:27                         ` Brad Templeton
2018-05-27  1:41                           ` Qu Wenruo
2018-05-27  1:49                             ` Brad Templeton
2018-05-27  1:56                               ` Qu Wenruo
2018-05-27  2:06                                 ` Brad Templeton
2018-05-27  2:16                                   ` Qu Wenruo
2018-05-27  2:21                                     ` Brad Templeton
2018-05-27  5:55                                       ` Duncan
2018-05-27 18:22                                       ` Brad Templeton
2018-05-28  8:31                                         ` Duncan
2018-06-08  3:23                           ` Zygo Blaxell
2016-03-27  4:23                     ` Brad Templeton
2016-03-23 21:54                 ` Duncan
2016-03-23 22:28               ` Duncan
2016-03-24  7:08               ` Andrew Vaughan

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=56F21510.6050707@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=bradtem@gmail.com \
    --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).