From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: remi@georgianit.com
Cc: Abdulla Bubshait <darkstego@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Array extremely unbalanced after convert to Raid5
Date: Wed, 5 May 2021 10:51:56 -0400 [thread overview]
Message-ID: <20210505145156.GC32440@hungrycats.org> (raw)
In-Reply-To: <5b563f2f-9057-44cc-8ec8-5367548aef6f@www.fastmail.com>
On Wed, May 05, 2021 at 09:58:03AM -0400, remi@georgianit.com wrote:
>
>
> On Wed, May 5, 2021, at 9:41 AM, Abdulla Bubshait wrote:
> > I ran a balance convert of my data single setup to raid 5. Once
> > complete the setup is extremely unbalanced and doesn't even make sense
> > as a raid 5. I tried to run a balance with dlimit of 1000, but it just
> > seems to make things worse.
>
> >
> > Unallocated:
> > /dev/sdd 14.12TiB
> > /dev/sdc 404.99GiB
> > /dev/sdf 1.00MiB
> > /dev/sde 1.00MiB
> >
> >
>
>
> Sorry, I don't have a solution for you, but I want to point out that
> the situation is far more critical than you seem to have realized.. this
> filesystem is now completely wedged, and I would suggest adding another
> device, or replacing either /dev/sdf or /dev/sde with something
> larger,, (though, if those are real disks, I see that might be a
> challenge.)
>
> Your metadata is Raid1C3, (meaning 3 copies,), but you only have 2 disks
> with free space. And thanks to the recent balancing, there is very
> little free space in the already allocated metadata,, so effectively,
> the filesystem can no longer write any new metadata and will very
> quickly hit out of space errors.
The situation isn't that dire. Balancing one data chunk off of either
/dev/sdf or /dev/sde will resolve the issue.
next prev parent reply other threads:[~2021-05-05 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 13:41 Array extremely unbalanced after convert to Raid5 Abdulla Bubshait
2021-05-05 13:58 ` remi
2021-05-05 14:23 ` Abdulla Bubshait
2021-05-05 14:51 ` Zygo Blaxell [this message]
2021-05-05 14:49 ` Zygo Blaxell
2021-05-05 15:35 ` Abdulla Bubshait
2021-05-06 4:32 ` Zygo Blaxell
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=20210505145156.GC32440@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=darkstego@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.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