.
I'm trying to fix it.
That sounds good but do you also get the
BTRFS: space_info 4 has 18446742286429913088 free, is not full
kernel messages on umount? if not you might have found another problem.
Yes, I seem similar messages, you can paste you whole dmesg info here.
[ cut here
;
>> And when compression is not enabled, you do not get ENOSPC error?
>
> I can't tell you. I cannot test with compression not enabled. I do not
> have anough free space on this disk.
>
>>>> I'm trying to fix it.
>>> That sounds good but do you also get th
into 4.9.
Yeah, good news :)
OK, I'll try to get these 2 patches merged, currently they still need
some code reviews from maintainers.
Regards,
Xiaoguang Wang
Greets,
Stefan
Regards,
Xiaoguang Wang
I'm trying to fix it.
That sounds good but do you also get the
BTRFS: space_info 4 has
t
> is 41844e36206be90cd4d962ea49b0abc3612a99d0.
no space errors since 5 days! that's currently amazing. I Hope it stays
this and your patches get into 4.9.
Greets,
Stefan
>
> Regards,
> Xiaoguang Wang
>
>>
>>>>> I'm trying to fix it.
>>>> That sounds
main difference between the system where oom happens is:
- Single Xeon => no OOM
- Dual Xeon / NUMA => OOM
both 64GB mem.
Am 07.10.2016 um 11:33 schrieb Holger Hoffstätte:
> On 10/07/16 09:17, Wang Xiaoguang wrote:
>> Hi,
>>
>> On 10/07/2016 03:03 PM, Stefan Priebe - Profihost AG wrote:
>>> Dear
n
> btrfs: improve inode's outstanding_extents computation
>
> I apply these two patchs in linux upstream tree, the latest commit
> is 41844e36206be90cd4d962ea49b0abc3612a99d0.
>
> Regards,
> Xiaoguang Wang
>
>>
>>>>> I'm trying to fix it.
>
Hi Holger,
Am 07.10.2016 um 11:33 schrieb Holger Hoffstätte:
> On 10/07/16 09:17, Wang Xiaoguang wrote:
>> Hi,
>>
>> On 10/07/2016 03:03 PM, Stefan Priebe - Profihost AG wrote:
>>> Dear Wang,
>>>
>>> can't use v4.8.0 as i always get OOMs and total machine crashes.
>>>
>>> Complete traces with
On 10/07/16 09:17, Wang Xiaoguang wrote:
> Hi,
>
> On 10/07/2016 03:03 PM, Stefan Priebe - Profihost AG wrote:
>> Dear Wang,
>>
>> can't use v4.8.0 as i always get OOMs and total machine crashes.
>>
>> Complete traces with your patch and some more btrfs patches applied (in
>> the hope in fixes
hat sounds good but do you also get the
BTRFS: space_info 4 has 18446742286429913088 free, is not full
kernel messages on umount? if not you might have found another
problem.
Yes, I seem similar messages, you can paste you whole dmesg info
here.
[ cut here ]
WARNING:
sion is not enabled, you do not get ENOSPC error?
>>>>>> I can't tell you. I cannot test with compression not enabled. I do
>>>>>> not
>>>>>> have anough free space on this disk.
>>>>> I had just sent two patches to fix false enospc error for co
outstanding_extents computation
I apply these two patchs in linux upstream tree, the latest commit
is 41844e36206be90cd4d962ea49b0abc3612a99d0.
Regards,
Xiaoguang Wang
I'm trying to fix it.
That sounds good but do you also get the
BTRFS: space_info 4 has 18446742286429913088 free, is not full
kernel messages
ches to fix false enospc error for compression,
>>> please have a try, they fix false enospc error in my test environment.
>>> btrfs: fix false enospc for compression
>>> btrfs: improve inode's outstanding_extents computation
>>>
>>> I apply these two
r compression
>>> btrfs: improve inode's outstanding_extents computation
>>>
>>> I apply these two patchs in linux upstream tree, the latest commit
>>> is 41844e36206be90cd4d962ea49b0abc3612a99d0.
>>>
>>> Regards,
>>> Xiaoguang
s to fix false enospc error for compression,
>>> please have a try, they fix false enospc error in my test environment.
>>> btrfs: fix false enospc for compression
>>> btrfs: improve inode's outstanding_extents computation
>>>
>>> I appl
@profihost.ag>; linux-btrfs@vger.kernel.org
> Subject: RE: BTRFS: space_info 4 has 18446742286429913088 free, is not full
>
>
> > -Original Message-
> > From: linux-btrfs-ow...@vger.kernel.org [mailto:linux-btrfs-
> > ow...@vger.kernel.org] On Behalf O
org
> Subject: Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full
>
> Hi,
>
> On 10/07/2016 03:03 PM, Stefan Priebe - Profihost AG wrote:
> > Dear Wang,
> >
> > can't use v4.8.0 as i always get OOMs and total machine crashes.
> >
> >
but do you also get the
BTRFS: space_info 4 has 18446742286429913088 free, is not full
kernel messages on umount? if not you might have found another problem.
Yes, I seem similar messages, you can paste you whole dmesg info here.
[ cut here ]
WARNING: CPU: 2 PID: 5187 at fs
pc error in my test environment.
> btrfs: fix false enospc for compression
> btrfs: improve inode's outstanding_extents computation
>
> I apply these two patchs in linux upstream tree, the latest commit
> is 41844e36206be90cd4d962ea49b0abc3612a99d0.
>
> Rega
n
> btrfs: improve inode's outstanding_extents computation
>
> I apply these two patchs in linux upstream tree, the latest commit
> is 41844e36206be90cd4d962ea49b0abc3612a99d0.
>
> Regards,
> Xiaoguang Wang
>
>>
>>>>> I'm trying to fix it.
>>>> That sounds good bu
n
> btrfs: improve inode's outstanding_extents computation
>
> I apply these two patchs in linux upstream tree, the latest commit
> is 41844e36206be90cd4d962ea49b0abc3612a99d0.
>
> Regards,
> Xiaoguang Wang
>
>>
>>>>> I'm trying to fix it.
>>>> That sounds good bu
upstream tree, the latest commit
is 41844e36206be90cd4d962ea49b0abc3612a99d0.
Regards,
Xiaoguang Wang
I'm trying to fix it.
That sounds good but do you also get the
BTRFS: space_info 4 has 18446742286429913088 free, is not full
kernel messages on umount? if not you might have found another problem
Hi,
Am 29.09.2016 um 12:03 schrieb Adam Borowski:
> On Thu, Sep 29, 2016 at 09:27:01AM +0200, Stefan Priebe - Profihost AG wrote:
>> Am 29.09.2016 um 09:13 schrieb Wang Xiaoguang:
> I found that compress sometime report ENOSPC error even in 4.8-rc8,
> currently
I cannot confirm that
On Thu, Sep 29, 2016 at 09:27:01AM +0200, Stefan Priebe - Profihost AG wrote:
> Am 29.09.2016 um 09:13 schrieb Wang Xiaoguang:
> >>> I found that compress sometime report ENOSPC error even in 4.8-rc8,
> >>> currently
> >> I cannot confirm that as i do not have anough space to test this without
>
>>> I'm trying to fix it.
>> That sounds good but do you also get the
>> BTRFS: space_info 4 has 18446742286429913088 free, is not full
>>
>> kernel messages on umount? if not you might have found another problem.
> Yes, I seem similar messages, you can paste yo
the
BTRFS: space_info 4 has 18446742286429913088 free, is not full
kernel messages on umount? if not you might have found another problem.
Yes, I seem similar messages, you can paste you whole dmesg info here.
Regards,
Xiaoguang Wang
Stefan
Regards,
Xiaoguang Wang
I tried hard to reproduce
do not have anough space to test this without
compression ;-( But yes i've compression enabled.
> I'm trying to fix it.
That sounds good but do you also get the
BTRFS: space_info 4 has 18446742286429913088 free, is not full
kernel messages on umount? if not you might have found another pr
Hi,
On 09/29/2016 02:49 PM, Stefan Priebe - Profihost AG wrote:
Hi,
Am 28.09.2016 um 14:10 schrieb Wang Xiaoguang:
OK, I see.
But given that you often run into enospc errors, can you work out a
reproduce
script according to you work load. That will give us great help.
You got ENOSPC errors
Hi,
Am 28.09.2016 um 14:10 schrieb Wang Xiaoguang:
> OK, I see.
> But given that you often run into enospc errors, can you work out a
> reproduce
> script according to you work load. That will give us great help.
I tried hard to reproduce it but i can't get it to reproduce with a test
script.
Am 28.09.2016 um 15:44 schrieb Holger Hoffstätte:
>> Good idea but it does not. I hope i can reproduce this with my already
>> existing testscript which i've now bumped to use a 37TB partition and
>> big files rather than a 15GB part and small files. If i can reproduce it
>> i can also check
On 09/28/16 15:06, Stefan Priebe - Profihost AG wrote:
>
> Yes this is 4.4.22 and no i don't have qgroups enabled so it can't help.
>
> # btrfs qgroup show /path/
> ERROR: can't perform the search - No such file or directory
> ERROR: can't list qgroups: No such file or director
>
> This is the
s there any chance anybody wants to work with me on the following issue?
>> Though I'm also somewhat new to btrfs, but I'd like to.
>>
>>>
>>> BTRFS: space_info 4 has 18446742286429913088 free, is not full
>>> BTRFS: space_info total=98247376896, used=77036814336
>> | BTRFS: space_info 4 has 18446743619906420736 free, is not full |
>> | BTRFS: space_info 4 has 18446743647369576448 free, is not full |
>> | BTRFS: space_info 4 has 18446742286429913088 free, is not full
>>
>> What i tried so far without success:
>> - use vanilla 4.8-r
PM, Stefan Priebe - Profihost AG wrote:
>>>> Dear list,
>>>>
>>>> is there any chance anybody wants to work with me on the following
>>>> issue?
>>> Though I'm also somewhat new to btrfs, but I'd like to.
>>>
>>>> BTRFS: space_inf
?
Though I'm also somewhat new to btrfs, but I'd like to.
BTRFS: space_info 4 has 18446742286429913088 free, is not full
BTRFS: space_info total=98247376896, used=77036814336, pinned=0,
reserved=0, may_use=1808490201088, readonly=0
i get this nearly every day.
Here are some msg collected from today
hat new to btrfs, but I'd like to.
>
>>
>> BTRFS: space_info 4 has 18446742286429913088 free, is not full
>> BTRFS: space_info total=98247376896, used=77036814336, pinned=0,
>> reserved=0, may_use=1808490201088, readonly=0
>>
>> i get this nearly every day.
>
Dear list,
is there any chance anybody wants to work with me on the following issue?
BTRFS: space_info 4 has 18446742286429913088 free, is not full
BTRFS: space_info total=98247376896, used=77036814336, pinned=0,
reserved=0, may_use=1808490201088, readonly=0
i get this nearly every day.
Here
36 matches
Mail list logo
