I already tried balancing with dusage=1. This removed all the allocated space.
It still doesn't allow me to do the conversion though, as it then reallocates
the space.
> On 27 okt. 2014, at 18:28, Chris Murphy wrote:
>
>
>> On Oct 27, 2014, at 10:54 AM, Jasper Verberk wrote:
>>
>> I actua
On Oct 27, 2014, at 10:54 AM, Jasper Verberk wrote:
> I actually tried going to raid1 with kernel 3.10 beforethe reason I
> updated to 3.17 was to see if this would fix the error.
>
> It still remained though….
If you have btrfs-progs you could do a btrfs check without repair and see if
I actually tried going to raid1 with kernel 3.10 beforethe reason I updated
to 3.17 was to see if this would fix the error.
It still remained though
> Subject: Re: Problem converting data raid0 to raid1: enospc errors during
> balance
On Oct 27, 2014, at 9:56 AM, Jasper Verberk wrote:
> These are the results to a normal df:
>
> http://paste.debian.net/128932/
>
> The mountpoint is /data.
OK so this is with the new computation in kernel 3.17 (which I think contains a
bug by counting free space twice); so now it shows avail
data raid0 to raid1: enospc errors during
> balance
>
>
> Original Message
> Subject: Re: Problem converting data raid0 to raid1: enospc errors
> during balance
> From: Chris Murphy
> To: Qu Wenruo
> Date: 2014年10月27日 12:40
>> On
>
> > On Oct 26, 2014, at 7:40 PM, Qu Wenruo wrote:
>
> BTW what's the output of 'df' command?
Jasper,
What do you get for the conventional df command when this btrfs volume is
mounted? Thanks.
Chris Murphy--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body o
Original Message
Subject: Re: Problem converting data raid0 to raid1: enospc errors
during balance
From: Chris Murphy
To: Qu Wenruo
Date: 2014年10月27日 12:40
On Oct 26, 2014, at 7:40 PM, Qu Wenruo wrote:
Hi,
Although I'm not completely sure, but it seems that, you r
On Oct 26, 2014, at 7:40 PM, Qu Wenruo 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
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 s
On Oct 24, 2014, at 11:49 AM, Jasper Verberk wrote:
> Did that, you can find the result in the pastebin.
>
> http://paste.debian.net/128552/
Maybe Josef or David will have some idea.
I'd still take a btrfs-image and btrfs check with current btrfs-progs.
Chris Murphy
--
To unsubscribe from t
Did that, you can find the result in the pastebin.
http://paste.debian.net/128552/
> Subject: Re: Problem converting data raid0 to raid1: enospc errors during
> balance
> From: li...@colorremedies.com
> Date: Fri, 24 Oct 2014 11:11:21 -0600
On Oct 24, 2014, at 7:32 AM, Jasper Verberk wrote:
>
> [60104.040776] BTRFS info (device sdc): 1046 enospc errors during balance
To get more information, remount with enospc_debug option, and try to convert
again.
> root@BlackMesa:/mnt# btrfs --version
> Btrfs v3.14.1
There are many fixes s
12 matches
Mail list logo
