From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Jasper Verberk <jverberk@hotmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Problem converting data raid0 to raid1: enospc errors during balance
Date: Mon, 27 Oct 2014 12:49:15 +0800 [thread overview]
Message-ID: <544DCECB.7060007@cn.fujitsu.com> (raw)
In-Reply-To: <1304C47B-8A9D-4AEA-B64A-C6566C77A5E1@colorremedies.com>
-------- Original Message --------
Subject: Re: Problem converting data raid0 to raid1: enospc errors
during balance
From: Chris Murphy <lists@colorremedies.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Date: 2014年10月27日 12:40
> On Oct 26, 2014, at 7:40 PM, Qu Wenruo <quwenruo@cn.fujitsu.com> wrote:
>
>> Hi,
>>
>> Although I'm not completely sure, but it seems that, you really ran out of space.
>>
>> [1] Your array won't hold raid1 for 1.97T data
>> Your array used up 1.97T raid0 data, it takes 1.97T for raid0.
>> But if converted to 1.97T, it will occupy 1.97T X2 = 3.94T.
>> Your array are only 2.73T, it is too small to contain the data.
> I'm not understanding. The btrfs fi show, shows 4x 2.73TiB devices, so that seems like it's a 10+TiB array.
>
> There's 2.04TiB raid0 data chunks, so roughly 500GiB per device, yet 1.94TiB is reported used per device by fi show. Confusing.
>
> Also it's still very confusing: Data, RAID1: total=2.85TiB, used=790.46GiB whether this means 2.85TiB out of 10TiB is allocated, or if it's twice that due to raid1. I can't ever remember this presentation detail, so again the secret decode ring where the UI doesn't expressly tell us what's going on is going to continue to be a source of confusion for users.
>
>
> Chris Murphy
Oh, I misread the output....
That turns strange now....
BTW what's the output of 'df' command?
Thanks,
Qu
next prev parent reply other threads:[~2014-10-27 4:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 13:32 Problem converting data raid0 to raid1: enospc errors during balance Jasper Verberk
2014-10-24 17:11 ` Chris Murphy
2014-10-24 17:49 ` Jasper Verberk
2014-10-24 18:19 ` Chris Murphy
2014-10-27 1:40 ` Qu Wenruo
2014-10-27 4:40 ` Chris Murphy
2014-10-27 4:49 ` Qu Wenruo [this message]
2014-10-27 16:04 ` Jasper Verberk
[not found] <DUB406-EAS294A0E4ED8B326281AFD7C6DA9E0@phx.gbl>
2014-10-27 15:19 ` Chris Murphy
[not found] ` <DUB118-W201FD897C8121E783F626CDA9E0@phx.gbl>
2014-10-27 16:43 ` Chris Murphy
2014-10-27 16:54 ` Jasper Verberk
2014-10-27 17:28 ` Chris Murphy
2014-10-27 17:38 ` Jasper Verberk
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=544DCECB.7060007@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=jverberk@hotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.