BTRFS: space_info 4 has 18446742286429913088 free, is not full

BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

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 are some msg collected from today and yesterday from different servers:
| BTRFS: space_info 4 has 18446742182612910080 free, is not full |
| BTRFS: space_info 4 has 18446742254739439616 free, is not full |
| BTRFS: space_info 4 has 18446743980225085440 free, is not full |
| 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-rc8 kernel
- use latest vanilla 4.4 kernel
- use latest 4.4 kernel + patches from holger hoffstaette
- use clear_cache,space_cache=v2
- use clear_cache,space_cache=v1

But all tries result in ENOSPC after a short period of time doing backups.

Greets,
Stefan

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

hello,

On 09/28/2016 07:15 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_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 and yesterday from different servers:
> | BTRFS: space_info 4 has 18446742182612910080 free, is not full |
> | BTRFS: space_info 4 has 18446742254739439616 free, is not full |
> | BTRFS: space_info 4 has 18446743980225085440 free, is not full |
> | 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-rc8 kernel
> - use latest vanilla 4.4 kernel
> - use latest 4.4 kernel + patches from holger hoffstaette
> - use clear_cache,space_cache=v2
> - use clear_cache,space_cache=v1
>
> But all tries result in ENOSPC after a short period of time doing backups.
I also met enospc error in 4.8-rc6 when doing big files create and 
delete tests,
for my cases, I have written some patches to fix it.
Would you please apply my patches to have a try:
btrfs: try to satisfy metadata requests when every flush_space() returns
btrfs: try to write enough delalloc bytes when reclaiming metadata space
btrfs: make shrink_delalloc() try harder to reclaim metadata space
You can find them in btrfs mail list.

Regards,
Xiaoguang Wang
>
> Greets,
> Stefan
> --
> 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
>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Hi Xiaoguang Wang,

Am 28.09.2016 um 13:35 schrieb Wang Xiaoguang:
> hello,
> 
> On 09/28/2016 07:15 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_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 and yesterday from different
>> servers:
>> | BTRFS: space_info 4 has 18446742182612910080 free, is not full |
>> | BTRFS: space_info 4 has 18446742254739439616 free, is not full |
>> | BTRFS: space_info 4 has 18446743980225085440 free, is not full |
>> | 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-rc8 kernel
>> - use latest vanilla 4.4 kernel
>> - use latest 4.4 kernel + patches from holger hoffstaette
>> - use clear_cache,space_cache=v2
>> - use clear_cache,space_cache=v1
>>
>> But all tries result in ENOSPC after a short period of time doing
>> backups.
> I also met enospc error in 4.8-rc6 when doing big files create and
> delete tests,
> for my cases, I have written some patches to fix it.
> Would you please apply my patches to have a try:
> btrfs: try to satisfy metadata requests when every flush_space() returns
> btrfs: try to write enough delalloc bytes when reclaiming metadata space
> btrfs: make shrink_delalloc() try harder to reclaim metadata space
> You can find them in btrfs mail list.

those are already in the patchset from holger:

So i have these in my testing patchset (latest 4.4 kernel + patches from
holger hoffstaette):

btrfs-20160921-try-to-satisfy-metadata-requests-when-every-flush_space()-returns.patch

btrfs-20160921-try-to-write-enough-delalloc-bytes-when-reclaiming-metadata-space.patch

btrfs-20160922-make-shrink_delalloc()-try-harder-to-reclaim-metadata-space.patch

Greets,
Stefan

> 
> Regards,
> Xiaoguang Wang
>>
>> Greets,
>> Stefan
>> -- 
>> 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
>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

hello,

On 09/28/2016 08:02 PM, Stefan Priebe - Profihost AG wrote:
> Hi Xiaoguang Wang,
>
> Am 28.09.2016 um 13:35 schrieb Wang Xiaoguang:
>> hello,
>>
>> On 09/28/2016 07:15 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_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 and yesterday from different
>>> servers:
>>> | BTRFS: space_info 4 has 18446742182612910080 free, is not full |
>>> | BTRFS: space_info 4 has 18446742254739439616 free, is not full |
>>> | BTRFS: space_info 4 has 18446743980225085440 free, is not full |
>>> | 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-rc8 kernel
>>> - use latest vanilla 4.4 kernel
>>> - use latest 4.4 kernel + patches from holger hoffstaette
>>> - use clear_cache,space_cache=v2
>>> - use clear_cache,space_cache=v1
>>>
>>> But all tries result in ENOSPC after a short period of time doing
>>> backups.
>> I also met enospc error in 4.8-rc6 when doing big files create and
>> delete tests,
>> for my cases, I have written some patches to fix it.
>> Would you please apply my patches to have a try:
>> btrfs: try to satisfy metadata requests when every flush_space() returns
>> btrfs: try to write enough delalloc bytes when reclaiming metadata space
>> btrfs: make shrink_delalloc() try harder to reclaim metadata space
>> You can find them in btrfs mail list.
> those are already in the patchset from holger:
>
> So i have these in my testing patchset (latest 4.4 kernel + patches from
> holger hoffstaette):
>
> btrfs-20160921-try-to-satisfy-metadata-requests-when-every-flush_space()-returns.patch
>
> btrfs-20160921-try-to-write-enough-delalloc-bytes-when-reclaiming-metadata-space.patch
>
> btrfs-20160922-make-shrink_delalloc()-try-harder-to-reclaim-metadata-space.patch
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.

Reagrds,
Xiaoguang Wang

>
> Greets,
> Stefan
>
>> Regards,
>> Xiaoguang Wang
>>> Greets,
>>> Stefan
>>> -- 
>>> 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
>>>
>>>
>>
>>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Am 28.09.2016 um 14:10 schrieb Wang Xiaoguang:
> hello,
> 
> On 09/28/2016 08:02 PM, Stefan Priebe - Profihost AG wrote:
>> Hi Xiaoguang Wang,
>>
>> Am 28.09.2016 um 13:35 schrieb Wang Xiaoguang:
>>> hello,
>>>
>>> On 09/28/2016 07:15 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_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 and yesterday from different
>>>> servers:
>>>> | BTRFS: space_info 4 has 18446742182612910080 free, is not full |
>>>> | BTRFS: space_info 4 has 18446742254739439616 free, is not full |
>>>> | BTRFS: space_info 4 has 18446743980225085440 free, is not full |
>>>> | 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-rc8 kernel
>>>> - use latest vanilla 4.4 kernel
>>>> - use latest 4.4 kernel + patches from holger hoffstaette
>>>> - use clear_cache,space_cache=v2
>>>> - use clear_cache,space_cache=v1
>>>>
>>>> But all tries result in ENOSPC after a short period of time doing
>>>> backups.
>>> I also met enospc error in 4.8-rc6 when doing big files create and
>>> delete tests,
>>> for my cases, I have written some patches to fix it.
>>> Would you please apply my patches to have a try:
>>> btrfs: try to satisfy metadata requests when every flush_space() returns
>>> btrfs: try to write enough delalloc bytes when reclaiming metadata space
>>> btrfs: make shrink_delalloc() try harder to reclaim metadata space
>>> You can find them in btrfs mail list.
>> those are already in the patchset from holger:
>>
>> So i have these in my testing patchset (latest 4.4 kernel + patches from
>> holger hoffstaette):
>>
>> btrfs-20160921-try-to-satisfy-metadata-requests-when-every-flush_space()-returns.patch
>>
>>
>> btrfs-20160921-try-to-write-enough-delalloc-bytes-when-reclaiming-metadata-space.patch
>>
>>
>> btrfs-20160922-make-shrink_delalloc()-try-harder-to-reclaim-metadata-space.patch
>>
> 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 already tried that but it wasn't working. It seems i need a test
device with +20TB and i need creating file that big in the tests. But
that isn't easy. Currently i've no test hardware that big. May be i
should try that on a production server.

Stefan

> Reagrds,
> Xiaoguang Wang
> 
>>
>> Greets,
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>> Greets,
>>>> Stefan
>>>> -- 
>>>> 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
>>>>
>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

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. Any ideas?

Stefan

> 
> Reagrds,
> Xiaoguang Wang
> 
>>
>> Greets,
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>> Greets,
>>>> Stefan
>>>> -- 
>>>> 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
>>>>
>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

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 only when you have compress enabled?

I found that compress sometime report ENOSPC error even in 4.8-rc8, 
currently
I'm trying to fix it.

Regards,
Xiaoguang Wang

> I tried hard to reproduce it but i can't get it to reproduce with a test
> script. Any ideas?
>
> Stefan
>
>> Reagrds,
>> Xiaoguang Wang
>>
>>> Greets,
>>> Stefan
>>>
>>>> Regards,
>>>> Xiaoguang Wang
>>>>> Greets,
>>>>> Stefan
>>>>> -- 
>>>>> 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
>>>>>
>>>>>
>>>>
>>
>>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Am 29.09.2016 um 08:55 schrieb Wang Xiaoguang:
> 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 only when you have compress enabled?
> 
> 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
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 problem.

Stefan

> 
> Regards,
> Xiaoguang Wang
> 
>> I tried hard to reproduce it but i can't get it to reproduce with a test
>> script. Any ideas?
>>
>> Stefan
>>
>>> Reagrds,
>>> Xiaoguang Wang
>>>
>>>> Greets,
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>> Greets,
>>>>>> Stefan
>>>>>> -- 
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

Hi,

On 09/29/2016 03:09 PM, Stefan Priebe - Profihost AG wrote:
> Am 29.09.2016 um 08:55 schrieb Wang Xiaoguang:
>> 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 only when you have compress enabled?
>>
>> 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
> compression ;-( But yes i've compression enabled.
I might not get you, my poor english :)
You mean that you only get ENOSPC error when compression is enabled?

And when compression is not enabled, you do not get ENOSPC error?
>
>> 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.

Regards,
Xiaoguang Wang

>
> Stefan
>
>> Regards,
>> Xiaoguang Wang
>>
>>> I tried hard to reproduce it but i can't get it to reproduce with a test
>>> script. Any ideas?
>>>
>>> Stefan
>>>
>>>> Reagrds,
>>>> Xiaoguang Wang
>>>>
>>>>> Greets,
>>>>> Stefan
>>>>>
>>>>>> Regards,
>>>>>> Xiaoguang Wang
>>>>>>> Greets,
>>>>>>> Stefan
>>>>>>> -- 
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>
>>
>>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

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
>> compression ;-( But yes i've compression enabled.
> I might not get you, my poor english :)
> You mean that you only get ENOSPC error when compression is enabled?
> 
> 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 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/btrfs/extent-tree.c:5790
btrfs_free_block_groups+0x346/0x430 [btrfs]()
Modules linked in: netconsole xt_multiport iptable_filter ip_tables
x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
Call Trace:
[<ffffffff813b69c3>] dump_stack+0x63/0x90
[<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
[<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
[<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
[<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
[<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
[<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
[<ffffffff811c8652>] kill_anon_super+0x12/0x20
[<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
[<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
[<ffffffff811c807c>] deactivate_super+0x5c/0x60
[<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
[<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
[<ffffffff8109dad1>] task_work_run+0x81/0xa0
[<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
[<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
[<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
---[ end trace cee6ace13018e13e ]---
------------[ cut here ]------------
WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
btrfs_free_block_groups+0x365/0x430 [btrfs]()
Modules linked in: netconsole xt_multiport iptable_filter ip_tables
x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
Call Trace:
[<ffffffff813b69c3>] dump_stack+0x63/0x90
[<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
[<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
[<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
[<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
[<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
[<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
[<ffffffff811c8652>] kill_anon_super+0x12/0x20
[<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
[<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
[<ffffffff811c807c>] deactivate_super+0x5c/0x60
[<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
[<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
[<ffffffff8109dad1>] task_work_run+0x81/0xa0
[<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
[<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
[<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
---[ end trace cee6ace13018e13f ]---
------------[ cut here ]------------
WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
btrfs_free_block_groups+0x291/0x430 [btrfs]()
Modules linked in: netconsole xt_multiport iptable_filter ip_tables
x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
Call Trace:
[<ffffffff813b69c3>] dump_stack+0x63/0x90
[<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
[<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
[<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
[<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
[<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
[<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
[<ffffffff811c8652>] kill_anon_super+0x12/0x20
[<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
[<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
[<ffffffff811c807c>] deactivate_super+0x5c/0x60
[<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
[<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
[<ffffffff8109dad1>] task_work_run+0x81/0xa0
[<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
[<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
[<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
---[ end trace cee6ace13018e140 ]---
BTRFS: space_info 4 has 18446742182612910080 free, is not full
BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
reserved=0, may_use=1908990066688, readonly=0

Greets,
Stefan

> Regards,
> Xiaoguang Wang
> 
>>
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>
>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>> test
>>>> script. Any ideas?
>>>>
>>>> Stefan
>>>>
>>>>> Reagrds,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> Greets,
>>>>>> Stefan
>>>>>>
>>>>>>> Regards,
>>>>>>> Xiaoguang Wang
>>>>>>>> Greets,
>>>>>>>> Stefan
>>>>>>>> -- 
>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[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 as i do not have anough space to test this without
> >> compression ;-( But yes i've compression enabled.
> > I might not get you, my poor english :)
> > You mean that you only get ENOSPC error when compression is enabled?
> > 
> > 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.

Disabling compression doesn't immediately require any space -- it affects
only newly written data.  What you already have remains in the old
compression setting, unless you defrag everything (a side effect of
defragging is switching existing extents to the new compression mode).

-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

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 as i do not have anough space to test this without
>>>> compression ;-( But yes i've compression enabled.
>>> I might not get you, my poor english :)
>>> You mean that you only get ENOSPC error when compression is enabled?
>>>
>>> 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.
> 
> Disabling compression doesn't immediately require any space -- it affects
> only newly written data.  What you already have remains in the old
> compression setting, unless you defrag everything (a side effect of
> defragging is switching existing extents to the new compression mode).

Yes i know that but most workload is creating reflinks to old files and
modify data in them. So to create a good test i need to defrag and
uncompress all those files.

Greets,
Stefan

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

Hi,

On 09/29/2016 03:27 PM, 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
>>> compression ;-( But yes i've compression enabled.
>> I might not get you, my poor english :)
>> You mean that you only get ENOSPC error when compression is enabled?
>>
>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
> btrfs_free_block_groups+0x346/0x430 [btrfs]()
> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
> Call Trace:
> [<ffffffff813b69c3>] dump_stack+0x63/0x90
> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
> ---[ end trace cee6ace13018e13e ]---
> ------------[ cut here ]------------
> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
> btrfs_free_block_groups+0x365/0x430 [btrfs]()
> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
> Call Trace:
> [<ffffffff813b69c3>] dump_stack+0x63/0x90
> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
> ---[ end trace cee6ace13018e13f ]---
> ------------[ cut here ]------------
> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
> btrfs_free_block_groups+0x291/0x430 [btrfs]()
> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
> Call Trace:
> [<ffffffff813b69c3>] dump_stack+0x63/0x90
> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
> ---[ end trace cee6ace13018e140 ]---
> BTRFS: space_info 4 has 18446742182612910080 free, is not full
> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
> reserved=0, may_use=1908990066688, readonly=0
>
> Greets,
> Stefan
>
>> Regards,
>> Xiaoguang Wang
>>
>>> Stefan
>>>
>>>> Regards,
>>>> Xiaoguang Wang
>>>>
>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>> test
>>>>> script. Any ideas?
>>>>>
>>>>> Stefan
>>>>>
>>>>>> Reagrds,
>>>>>> Xiaoguang Wang
>>>>>>
>>>>>>> Greets,
>>>>>>> Stefan
>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Xiaoguang Wang
>>>>>>>>> Greets,
>>>>>>>>> Stefan
>>>>>>>>> -- 
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>
>>
>>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Thanks Wang,

i applied them both on top of vanilla v4.8 - i hope this is OK. Will
report back what happens.

Greets,
Stefan

Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
> Hi,
> 
> On 09/29/2016 03:27 PM, 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
>>>> compression ;-( But yes i've compression enabled.
>>> I might not get you, my poor english :)
>>> You mean that you only get ENOSPC error when compression is enabled?
>>>
>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13e ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13f ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e140 ]---
>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>> reserved=0, may_use=1908990066688, readonly=0
>>
>> Greets,
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>> test
>>>>>> script. Any ideas?
>>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Reagrds,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> Greets,
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>> -- 
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Thanks Wang,

i applied them both on top of vanilla v4.8 - i hope this is OK. Will
report back what happens.

Greets,
Stefan

Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
> Hi,
> 
> On 09/29/2016 03:27 PM, 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
>>>> compression ;-( But yes i've compression enabled.
>>> I might not get you, my poor english :)
>>> You mean that you only get ENOSPC error when compression is enabled?
>>>
>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13e ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13f ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e140 ]---
>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>> reserved=0, may_use=1908990066688, readonly=0
>>
>> Greets,
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>> test
>>>>>> script. Any ideas?
>>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Reagrds,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> Greets,
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>> -- 
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

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 the OOM but it did not):
http://pastebin.com/raw/6vmRSDm1

Greets,
Stefan
Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
> Hi,
> 
> On 09/29/2016 03:27 PM, 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
>>>> compression ;-( But yes i've compression enabled.
>>> I might not get you, my poor english :)
>>> You mean that you only get ENOSPC error when compression is enabled?
>>>
>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13e ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13f ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e140 ]---
>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>> reserved=0, may_use=1908990066688, readonly=0
>>
>> Greets,
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>> test
>>>>>> script. Any ideas?
>>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Reagrds,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> Greets,
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>> -- 
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

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 the OOM but it did not):
> http://pastebin.com/raw/6vmRSDm1
I didn't see any such OOMs...
Can you try holger's tree with my patches.

Regards,
Xiaoguang Wang
>
> Greets,
> Stefan
> Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
>> Hi,
>>
>> On 09/29/2016 03:27 PM, 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
>>>>> compression ;-( But yes i've compression enabled.
>>>> I might not get you, my poor english :)
>>>> You mean that you only get ENOSPC error when compression is enabled?
>>>>
>>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>> Call Trace:
>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>> ---[ end trace cee6ace13018e13e ]---
>>> ------------[ cut here ]------------
>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>> Call Trace:
>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>> ---[ end trace cee6ace13018e13f ]---
>>> ------------[ cut here ]------------
>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>>> Call Trace:
>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>> ---[ end trace cee6ace13018e140 ]---
>>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>>> reserved=0, may_use=1908990066688, readonly=0
>>>
>>> Greets,
>>> Stefan
>>>
>>>> Regards,
>>>> Xiaoguang Wang
>>>>
>>>>> Stefan
>>>>>
>>>>>> Regards,
>>>>>> Xiaoguang Wang
>>>>>>
>>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>>> test
>>>>>>> script. Any ideas?
>>>>>>>
>>>>>>> Stefan
>>>>>>>
>>>>>>>> Reagrds,
>>>>>>>> Xiaoguang Wang
>>>>>>>>
>>>>>>>>> Greets,
>>>>>>>>> Stefan
>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>> Greets,
>>>>>>>>>>> Stefan
>>>>>>>>>>> -- 
>>>>>>>>>>> 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
>>>>>>>>>>>
>>>>>>>>>>>
>>>>
>>
>>
>

RE: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Paul Jones]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 990 bytes --]


> -----Original Message-----
> From: linux-btrfs-owner@vger.kernel.org [mailto:linux-btrfs-
> owner@vger.kernel.org] On Behalf Of Wang Xiaoguang
> Sent: Friday, 7 October 2016 6:17 PM
> To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>; linux-
> btrfs@vger.kernel.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.
> >
> > Complete traces with your patch and some more btrfs patches applied
> > (in the hope in fixes the OOM but it did not):
> > http://pastebin.com/raw/6vmRSDm1
> I didn't see any such OOMs...
> Can you try holger's tree with my patches.
> 
> Regards,
> Xiaoguang Wang
> >


4.8.5 has fixed all the OOM problems for me, so try that one.

Paul.
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±ý»k~ÏâžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣøm

RE: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Paul Jones]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1484 bytes --]

> -----Original Message-----
> From: linux-btrfs-owner@vger.kernel.org [mailto:linux-btrfs-
> owner@vger.kernel.org] On Behalf Of Paul Jones
> Sent: Friday, 7 October 2016 6:48 PM
> To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>; Stefan Priebe -
> Profihost AG <s.priebe@profihost.ag>; linux-btrfs@vger.kernel.org
> Subject: RE: BTRFS: space_info 4 has 18446742286429913088 free, is not full
> 
> 
> > -----Original Message-----
> > From: linux-btrfs-owner@vger.kernel.org [mailto:linux-btrfs-
> > owner@vger.kernel.org] On Behalf Of Wang Xiaoguang
> > Sent: Friday, 7 October 2016 6:17 PM
> > To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>; linux-
> > btrfs@vger.kernel.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.
> > >
> > > Complete traces with your patch and some more btrfs patches applied
> > > (in the hope in fixes the OOM but it did not):
> > > http://pastebin.com/raw/6vmRSDm1
> > I didn't see any such OOMs...
> > Can you try holger's tree with my patches.
> >
> > Regards,
> > Xiaoguang Wang
> > >
> 
> 
> 4.8.5 has fixed all the OOM problems for me, so try that one.

Sorry, just realised I meant 4.7.5!

Paul.




ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±ý»k~ÏâžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣøm

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Am 07.10.2016 um 09:17 schrieb Wang Xiaoguang:
> 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 the OOM but it did not):
>> http://pastebin.com/raw/6vmRSDm1
> I didn't see any such OOMs...
> Can you try holger's tree with my patches.

Dear wang already tried that. Doesn't help. It also happens only on two
out of three servers.  It starts killing low men processes after time.
But I've no idea where all those memory is consumed. (Have 64gb)

Greets,
Stefan


> Regards,
> Xiaoguang Wang
>>
>> Greets,
>> Stefan
>> Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
>>> Hi,
>>>
>>> On 09/29/2016 03:27 PM, 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
>>>>>> compression ;-( But yes i've compression enabled.
>>>>> I might not get you, my poor english :)
>>>>> You mean that you only get ENOSPC error when compression is enabled?
>>>>>
>>>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>>>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e13e ]---
>>>> ------------[ cut here ]------------
>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>>>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e13f ]---
>>>> ------------[ cut here ]------------
>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>>>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>>>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e140 ]---
>>>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>>>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>>>> reserved=0, may_use=1908990066688, readonly=0
>>>>
>>>> Greets,
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Regards,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>>>> test
>>>>>>>> script. Any ideas?
>>>>>>>>
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Reagrds,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>>> Greets,
>>>>>>>>>>>> Stefan
>>>>>>>>>>>> -- 
>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

this is what atop shows at mem usage 5 minutes before the crash:

MEM | tot    62.8G  | free  198.2M  | cache  56.8G  | buff    1.4M |
slab    3.5G |  shmem   1.1M |  vmbal   0.0M |  hptot   0.0M |

SWP | tot     3.7G  | free    3.2G  |               |              |
          |               |  vmcom   2.8G |  vmlim  35.1G |

Greets,
Stefan

Am 07.10.2016 um 09:17 schrieb Wang Xiaoguang:
> 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 the OOM but it did not):
>> http://pastebin.com/raw/6vmRSDm1
> I didn't see any such OOMs...
> Can you try holger's tree with my patches.
> 
> Regards,
> Xiaoguang Wang
>>
>> Greets,
>> Stefan
>> Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
>>> Hi,
>>>
>>> On 09/29/2016 03:27 PM, 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
>>>>>> compression ;-( But yes i've compression enabled.
>>>>> I might not get you, my poor english :)
>>>>> You mean that you only get ENOSPC error when compression is enabled?
>>>>>
>>>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>>>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e13e ]---
>>>> ------------[ cut here ]------------
>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>>>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e13f ]---
>>>> ------------[ cut here ]------------
>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>>>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>>>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e140 ]---
>>>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>>>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>>>> reserved=0, may_use=1908990066688, readonly=0
>>>>
>>>> Greets,
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Regards,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>>>> test
>>>>>>>> script. Any ideas?
>>>>>>>>
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Reagrds,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>>> Greets,
>>>>>>>>>>>> Stefan
>>>>>>>>>>>> -- 
>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

and it shows:

PAG | scan 33829e5  | steal 1968e3  | stall      0  |              |
          |               |  swin  257071 |  swout 346960 |

but the highest user space prog uses only 190MB.

greets,
Stefan

Am 07.10.2016 um 09:17 schrieb Wang Xiaoguang:
> 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 the OOM but it did not):
>> http://pastebin.com/raw/6vmRSDm1
> I didn't see any such OOMs...
> Can you try holger's tree with my patches.
> 
> Regards,
> Xiaoguang Wang
>>
>> Greets,
>> Stefan
>> Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
>>> Hi,
>>>
>>> On 09/29/2016 03:27 PM, 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
>>>>>> compression ;-( But yes i've compression enabled.
>>>>> I might not get you, my poor english :)
>>>>> You mean that you only get ENOSPC error when compression is enabled?
>>>>>
>>>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>>>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e13e ]---
>>>> ------------[ cut here ]------------
>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>>>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e13f ]---
>>>> ------------[ cut here ]------------
>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>>>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>>>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>>>> Call Trace:
>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>> ---[ end trace cee6ace13018e140 ]---
>>>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>>>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>>>> reserved=0, may_use=1908990066688, readonly=0
>>>>
>>>> Greets,
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Regards,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>>>> test
>>>>>>>> script. Any ideas?
>>>>>>>>
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Reagrds,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>>> Greets,
>>>>>>>>>>>> Stefan
>>>>>>>>>>>> -- 
>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

hello,

On 10/07/2016 04:06 PM, Stefan Priebe - Profihost AG wrote:
> and it shows:
>
> PAG | scan 33829e5  | steal 1968e3  | stall      0  |              |
>            |               |  swin  257071 |  swout 346960 |
>
> but the highest user space prog uses only 190MB.
If you don't apply my patches, there will be no OOMs in your test 
environment?
I want to confirm whether this OOM is caused by my patches...

Regards,
Xiaoguang Wang

>
> greets,
> Stefan
>
> Am 07.10.2016 um 09:17 schrieb Wang Xiaoguang:
>> 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 the OOM but it did not):
>>> http://pastebin.com/raw/6vmRSDm1
>> I didn't see any such OOMs...
>> Can you try holger's tree with my patches.
>>
>> Regards,
>> Xiaoguang Wang
>>> Greets,
>>> Stefan
>>> Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
>>>> Hi,
>>>>
>>>> On 09/29/2016 03:27 PM, 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
>>>>>>> compression ;-( But yes i've compression enabled.
>>>>>> I might not get you, my poor english :)
>>>>>> You mean that you only get ENOSPC error when compression is enabled?
>>>>>>
>>>>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>>>>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>>> Call Trace:
>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>> ---[ end trace cee6ace13018e13e ]---
>>>>> ------------[ cut here ]------------
>>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>>>>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>>> Call Trace:
>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>> ---[ end trace cee6ace13018e13f ]---
>>>>> ------------[ cut here ]------------
>>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>>>>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>>>>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>>>>> Call Trace:
>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>> ---[ end trace cee6ace13018e140 ]---
>>>>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>>>>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>>>>> reserved=0, may_use=1908990066688, readonly=0
>>>>>
>>>>> Greets,
>>>>> Stefan
>>>>>
>>>>>> Regards,
>>>>>> Xiaoguang Wang
>>>>>>
>>>>>>> Stefan
>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Xiaoguang Wang
>>>>>>>>
>>>>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>>>>> test
>>>>>>>>> script. Any ideas?
>>>>>>>>>
>>>>>>>>> Stefan
>>>>>>>>>
>>>>>>>>>> Reagrds,
>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>
>>>>>>>>>>> Greets,
>>>>>>>>>>> Stefan
>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>>>> Greets,
>>>>>>>>>>>>> Stefan
>>>>>>>>>>>>> -- 
>>>>>>>>>>>>> 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
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>
>>
>>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Am 07.10.2016 um 10:07 schrieb Wang Xiaoguang:
> hello,
> 
> On 10/07/2016 04:06 PM, Stefan Priebe - Profihost AG wrote:
>> and it shows:
>>
>> PAG | scan 33829e5  | steal 1968e3  | stall      0  |              |
>>            |               |  swin  257071 |  swout 346960 |
>>
>> but the highest user space prog uses only 190MB.
> If you don't apply my patches, there will be no OOMs in your test
> environment?
> I want to confirm whether this OOM is caused by my patches...

This happens also without your patches. That's what i meant with can't
use v4.8.0.

Is it OK to try v4.7.6?

Greets,
Stefan

> 
> Regards,
> Xiaoguang Wang
> 
>>
>> greets,
>> Stefan
>>
>> Am 07.10.2016 um 09:17 schrieb Wang Xiaoguang:
>>> 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 the OOM but it did not):
>>>> http://pastebin.com/raw/6vmRSDm1
>>> I didn't see any such OOMs...
>>> Can you try holger's tree with my patches.
>>>
>>> Regards,
>>> Xiaoguang Wang
>>>> Greets,
>>>> Stefan
>>>> Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
>>>>> Hi,
>>>>>
>>>>> On 09/29/2016 03:27 PM, 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
>>>>>>>> compression ;-( But yes i've compression enabled.
>>>>>>> I might not get you, my poor english :)
>>>>>>> You mean that you only get ENOSPC error when compression is enabled?
>>>>>>>
>>>>>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>>>>>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp
>>>>>> kvm_intel kvm
>>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb
>>>>>> i2c_algo_bit
>>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>>>> Call Trace:
>>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>>> ---[ end trace cee6ace13018e13e ]---
>>>>>> ------------[ cut here ]------------
>>>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>>>>>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp
>>>>>> kvm_intel kvm
>>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb
>>>>>> i2c_algo_bit
>>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>>>> Call Trace:
>>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>>> ---[ end trace cee6ace13018e13f ]---
>>>>>> ------------[ cut here ]------------
>>>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>>>>>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp
>>>>>> kvm_intel kvm
>>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb
>>>>>> i2c_algo_bit
>>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>>>>>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>>>>>> Call Trace:
>>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>>> ---[ end trace cee6ace13018e140 ]---
>>>>>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>>>>>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>>>>>> reserved=0, may_use=1908990066688, readonly=0
>>>>>>
>>>>>> Greets,
>>>>>> Stefan
>>>>>>
>>>>>>> Regards,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>
>>>>>>>>>> I tried hard to reproduce it but i can't get it to reproduce
>>>>>>>>>> with a
>>>>>>>>>> test
>>>>>>>>>> script. Any ideas?
>>>>>>>>>>
>>>>>>>>>> Stefan
>>>>>>>>>>
>>>>>>>>>>> Reagrds,
>>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>>
>>>>>>>>>>>> Greets,
>>>>>>>>>>>> Stefan
>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>>>>> Greets,
>>>>>>>>>>>>>> Stefan
>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

hello,

On 10/07/2016 04:16 PM, Stefan Priebe - Profihost AG wrote:
> Am 07.10.2016 um 10:07 schrieb Wang Xiaoguang:
>> hello,
>>
>> On 10/07/2016 04:06 PM, Stefan Priebe - Profihost AG wrote:
>>> and it shows:
>>>
>>> PAG | scan 33829e5  | steal 1968e3  | stall      0  |              |
>>>             |               |  swin  257071 |  swout 346960 |
>>>
>>> but the highest user space prog uses only 190MB.
>> If you don't apply my patches, there will be no OOMs in your test
>> environment?
>> I want to confirm whether this OOM is caused by my patches...
> This happens also without your patches. That's what i meant with can't
> use v4.8.0.
>
> Is it OK to try v4.7.6?
OK, I see.
I think you can have a try :)
Paul Jones has mentioned that "4.7.5 has fixed all the OOM problems for 
me, so try that one."

Regards,
XIaoguang Wang

>
> Greets,
> Stefan
>
>> Regards,
>> Xiaoguang Wang
>>
>>> greets,
>>> Stefan
>>>
>>> Am 07.10.2016 um 09:17 schrieb Wang Xiaoguang:
>>>> 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 the OOM but it did not):
>>>>> http://pastebin.com/raw/6vmRSDm1
>>>> I didn't see any such OOMs...
>>>> Can you try holger's tree with my patches.
>>>>
>>>> Regards,
>>>> Xiaoguang Wang
>>>>> Greets,
>>>>> Stefan
>>>>> Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
>>>>>> Hi,
>>>>>>
>>>>>> On 09/29/2016 03:27 PM, 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
>>>>>>>>> compression ;-( But yes i've compression enabled.
>>>>>>>> I might not get you, my poor english :)
>>>>>>>> You mean that you only get ENOSPC error when compression is enabled?
>>>>>>>>
>>>>>>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>>>>>>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>>>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp
>>>>>>> kvm_intel kvm
>>>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb
>>>>>>> i2c_algo_bit
>>>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>>>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>>>>> Call Trace:
>>>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>>>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>>>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>>>> ---[ end trace cee6ace13018e13e ]---
>>>>>>> ------------[ cut here ]------------
>>>>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>>>>>>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>>>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp
>>>>>>> kvm_intel kvm
>>>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb
>>>>>>> i2c_algo_bit
>>>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>>>>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>>>>>> Call Trace:
>>>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>>>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>>>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>>>> ---[ end trace cee6ace13018e13f ]---
>>>>>>> ------------[ cut here ]------------
>>>>>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>>>>>>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>>>>>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>>>>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp
>>>>>>> kvm_intel kvm
>>>>>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>>>>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>>>>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>>>>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb
>>>>>>> i2c_algo_bit
>>>>>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>>>>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>>>>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>>>>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>>>>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>>>>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>>>>>>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>>>>>>> Call Trace:
>>>>>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>>>>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>>>>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>>>>>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>>>>>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>>>>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>>>>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>>>>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>>>>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>>>>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>>>>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>>>>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>>>>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>>>>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>>>>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>>>>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>>>>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>>>>>> ---[ end trace cee6ace13018e140 ]---
>>>>>>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>>>>>>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>>>>>>> reserved=0, may_use=1908990066688, readonly=0
>>>>>>>
>>>>>>> Greets,
>>>>>>> Stefan
>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Xiaoguang Wang
>>>>>>>>
>>>>>>>>> Stefan
>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>
>>>>>>>>>>> I tried hard to reproduce it but i can't get it to reproduce
>>>>>>>>>>> with a
>>>>>>>>>>> test
>>>>>>>>>>> script. Any ideas?
>>>>>>>>>>>
>>>>>>>>>>> Stefan
>>>>>>>>>>>
>>>>>>>>>>>> Reagrds,
>>>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>>>
>>>>>>>>>>>>> Greets,
>>>>>>>>>>>>> Stefan
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>>>>>> Greets,
>>>>>>>>>>>>>>> Stefan
>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>
>>
>>
> --
> 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
>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[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 your patch and some more btrfs patches applied (in
>> the hope in fixes the OOM but it did not):
>> http://pastebin.com/raw/6vmRSDm1
> I didn't see any such OOMs...
> Can you try holger's tree with my patches.

They don't really apply to either 4.4.x (because it has diverged too
much by now) or 4.8.x because of the initial dedupe support which came
in as part of 4.9rc1 - there are way too many conflicts all over the
place and merging them manually took way too much time.
It would be useful if you could rebase your patches to for-next.

Stefan, have you tried setting THP to 'madvise' or 'never'?
Try 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled'
or boot with transparent_hugepage=madvise (or never) kernel flag.
I have no idea if it will help, but it's worth a try.

-h

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

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 your patch and some more btrfs patches applied (in
>>> the hope in fixes the OOM but it did not):
>>> http://pastebin.com/raw/6vmRSDm1
>> I didn't see any such OOMs...
>> Can you try holger's tree with my patches.
> 
> They don't really apply to either 4.4.x (because it has diverged too
> much by now) or 4.8.x because of the initial dedupe support which came
> in as part of 4.9rc1 - there are way too many conflicts all over the
> place and merging them manually took way too much time.
> It would be useful if you could rebase your patches to for-next.
> 
> Stefan, have you tried setting THP to 'madvise' or 'never'?
> Try 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled'
> or boot with transparent_hugepage=madvise (or never) kernel flag.
> I have no idea if it will help, but it's worth a try.

It's already set to never. The hosts are currently still up and running
but only if i run
echo 3 >/proc/sys/vm/drop_caches

every 30 minutes. It seems the kernel fails to reclaim the cache itself
if user space needs memory.

Greets,
Stefan

> 
> -h
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

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 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 the OOM but it did not):
>>> http://pastebin.com/raw/6vmRSDm1
>> I didn't see any such OOMs...
>> Can you try holger's tree with my patches.
> 
> They don't really apply to either 4.4.x (because it has diverged too
> much by now) or 4.8.x because of the initial dedupe support which came
> in as part of 4.9rc1 - there are way too many conflicts all over the
> place and merging them manually took way too much time.
> It would be useful if you could rebase your patches to for-next.
> 
> Stefan, have you tried setting THP to 'madvise' or 'never'?
> Try 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled'
> or boot with transparent_hugepage=madvise (or never) kernel flag.
> I have no idea if it will help, but it's worth a try.
> 
> -h
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Hi Wang,

currently on the system where it's working fine - no ENOSPC error. But
it will take a week to be sure they don't come back.

Thanks!

Greets,
Stefan
Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
> Hi,
> 
> On 09/29/2016 03:27 PM, 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
>>>> compression ;-( But yes i've compression enabled.
>>> I might not get you, my poor english :)
>>> You mean that you only get ENOSPC error when compression is enabled?
>>>
>>> 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 had just sent two patches 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 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 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/btrfs/extent-tree.c:5790
>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13e ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13f ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e140 ]---
>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>> reserved=0, may_use=1908990066688, readonly=0
>>
>> Greets,
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>> test
>>>>>> script. Any ideas?
>>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Reagrds,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> Greets,
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>> -- 
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Dear Wang,

Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
> Hi,
> 
> On 09/29/2016 03:27 PM, 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
>>>> compression ;-( But yes i've compression enabled.
>>> I might not get you, my poor english :)
>>> You mean that you only get ENOSPC error when compression is enabled?
>>>
>>> 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 had just sent two patches 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 patchs in linux upstream tree, the latest commit
> 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 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: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5790
>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13e ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13f ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e140 ]---
>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>> reserved=0, may_use=1908990066688, readonly=0
>>
>> Greets,
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>> test
>>>>>> script. Any ideas?
>>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Reagrds,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> Greets,
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>> -- 
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>
>>>
>>
> 
> 
> 

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

hi,

On 10/11/2016 04:06 AM, Stefan Priebe - Profihost AG wrote:
> Dear Wang,
>
> Am 06.10.2016 um 05:04 schrieb Wang Xiaoguang:
>> Hi,
>>
>> On 09/29/2016 03:27 PM, 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
>>>>> compression ;-( But yes i've compression enabled.
>>>> I might not get you, my poor english :)
>>>> You mean that you only get ENOSPC error when compression is enabled?
>>>>
>>>> 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 had just sent two patches 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 patchs in linux upstream tree, the latest commit
>> is 41844e36206be90cd4d962ea49b0abc3612a99d0.
> no space errors since 5 days! that's currently amazing. I Hope it stays
> this and your patches get 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 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/btrfs/extent-tree.c:5790
>>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>> Call Trace:
>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>> ---[ end trace cee6ace13018e13e ]---
>>> ------------[ cut here ]------------
>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>>> Call Trace:
>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>> ---[ end trace cee6ace13018e13f ]---
>>> ------------[ cut here ]------------
>>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>>> Call Trace:
>>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>>> ---[ end trace cee6ace13018e140 ]---
>>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>>> reserved=0, may_use=1908990066688, readonly=0
>>>
>>> Greets,
>>> Stefan
>>>
>>>> Regards,
>>>> Xiaoguang Wang
>>>>
>>>>> Stefan
>>>>>
>>>>>> Regards,
>>>>>> Xiaoguang Wang
>>>>>>
>>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>>> test
>>>>>>> script. Any ideas?
>>>>>>>
>>>>>>> Stefan
>>>>>>>
>>>>>>>> Reagrds,
>>>>>>>> Xiaoguang Wang
>>>>>>>>
>>>>>>>>> Greets,
>>>>>>>>> Stefan
>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Xiaoguang Wang
>>>>>>>>>>> Greets,
>>>>>>>>>>> Stefan
>>>>>>>>>>> -- 
>>>>>>>>>>> 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
>>>>>>>>>>>
>>>>>>>>>>>
>>>>
>>
>>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Hello list,

just wanted to report that my ENOSPC errors are gone. Thanks to wang for
his great patches.

but the space_info corruption still occours.

On every umount i see:
[93022.166222] BTRFS: space_info 4 has 208952672256 free, is not full
[93022.166224] BTRFS: space_info total=363998478336, used=155045216256,
pinned=0, reserved=0, may_use=524288, readonly=65536

Greets,
Stefan

Am 29.09.2016 um 09:27 schrieb Stefan Priebe - Profihost AG:
> 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
>>> compression ;-( But yes i've compression enabled.
>> I might not get you, my poor english :)
>> You mean that you only get ENOSPC error when compression is enabled?
>>
>> 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 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/btrfs/extent-tree.c:5790
> btrfs_free_block_groups+0x346/0x430 [btrfs]()
> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
> Call Trace:
> [<ffffffff813b69c3>] dump_stack+0x63/0x90
> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
> ---[ end trace cee6ace13018e13e ]---
> ------------[ cut here ]------------
> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
> btrfs_free_block_groups+0x365/0x430 [btrfs]()
> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
> Call Trace:
> [<ffffffff813b69c3>] dump_stack+0x63/0x90
> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
> ---[ end trace cee6ace13018e13f ]---
> ------------[ cut here ]------------
> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
> btrfs_free_block_groups+0x291/0x430 [btrfs]()
> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
> Call Trace:
> [<ffffffff813b69c3>] dump_stack+0x63/0x90
> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
> ---[ end trace cee6ace13018e140 ]---
> BTRFS: space_info 4 has 18446742182612910080 free, is not full
> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
> reserved=0, may_use=1908990066688, readonly=0
> 
> Greets,
> Stefan
> 
>> Regards,
>> Xiaoguang Wang
>>
>>>
>>> Stefan
>>>
>>>> Regards,
>>>> Xiaoguang Wang
>>>>
>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>> test
>>>>> script. Any ideas?
>>>>>
>>>>> Stefan
>>>>>
>>>>>> Reagrds,
>>>>>> Xiaoguang Wang
>>>>>>
>>>>>>> Greets,
>>>>>>> Stefan
>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Xiaoguang Wang
>>>>>>>>> Greets,
>>>>>>>>> Stefan
>>>>>>>>> -- 
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>
>>
>>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Wang Xiaoguang]

hi,

On 10/24/2016 01:47 AM, Stefan Priebe - Profihost AG wrote:
> Hello list,
>
> just wanted to report that my ENOSPC errors are gone. Thanks to wang for
> his great patches.
>
> but the space_info corruption still occours.
>
> On every umount i see:
> [93022.166222] BTRFS: space_info 4 has 208952672256 free, is not full
> [93022.166224] BTRFS: space_info total=363998478336, used=155045216256,
> pinned=0, reserved=0, may_use=524288, readonly=65536
I see. Could you provide your mount options  and kernel version(git 
repertory), then
I can look into the codes :)

Regards,
Xiaoguang Wang

>
> Greets,
> Stefan
>
> Am 29.09.2016 um 09:27 schrieb Stefan Priebe - Profihost AG:
>> 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
>>>> compression ;-( But yes i've compression enabled.
>>> I might not get you, my poor english :)
>>> You mean that you only get ENOSPC error when compression is enabled?
>>>
>>> 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 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/btrfs/extent-tree.c:5790
>> btrfs_free_block_groups+0x346/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9a6>] btrfs_free_block_groups+0x346/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13e ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:5791
>> btrfs_free_block_groups+0x365/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 0000000000000000
>> ffff880074bf0a00 ffff88103c10c088 ffff88103c10c000 ffff88103c10c098
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de9c5>] btrfs_free_block_groups+0x365/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e13f ]---
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 5187 at fs/btrfs/extent-tree.c:10151
>> btrfs_free_block_groups+0x291/0x430 [btrfs]()
>> Modules linked in: netconsole xt_multiport iptable_filter ip_tables
>> x_tables 8021q garp bonding x86_pkg_temp_thermal coretemp kvm_intel kvm
>> irqbypass sb_edac crc32_pclmul edac_core i2c_i801 i40e(O) vxlan
>> ip6_udp_tunnel udp_tunnel shpchp ipmi_si ipmi_msghandler button loop
>> btrfs dm_mod raid10 raid0 multipath linear raid456 async_raid6_recov
>> async_memcpy async_pq async_xor async_tx xor raid6_pq igb i2c_algo_bit
>> i2c_core usbhid raid1 md_mod xhci_pci sg ehci_pci xhci_hcd ehci_hcd
>> sd_mod ahci usbcore ptp libahci usb_common pps_core aacraid
>> CPU: 2 PID: 5187 Comm: umount Tainted: G W O 4.4.22+63-ph #1
>> Hardware name: Supermicro Super Server/X10SRi-F, BIOS 2.0 12/17/2015
>> 0000000000000000 ffff880fda777d00 ffffffff813b69c3 0000000000000000
>> ffffffffc067a099 ffff880fda777d38 ffffffff810821c6 ffff880074bf0000
>> ffff880074bf0088 ffff880074bf0df8 ffff88103c10c000 0000000000000000
>> Call Trace:
>> [<ffffffff813b69c3>] dump_stack+0x63/0x90
>> [<ffffffff810821c6>] warn_slowpath_common+0x86/0xc0
>> [<ffffffff810822ba>] warn_slowpath_null+0x1a/0x20
>> [<ffffffffc05de8f1>] btrfs_free_block_groups+0x291/0x430 [btrfs]
>> [<ffffffffc05f0bad>] close_ctree+0x15d/0x330 [btrfs]
>> [<ffffffffc05bf409>] btrfs_put_super+0x19/0x20 [btrfs]
>> [<ffffffff811c85af>] generic_shutdown_super+0x6f/0x100
>> [<ffffffff811c8652>] kill_anon_super+0x12/0x20
>> [<ffffffffc05c0376>] btrfs_kill_super+0x16/0xa0 [btrfs]
>> [<ffffffff811c7ff3>] deactivate_locked_super+0x43/0x70
>> [<ffffffff811c807c>] deactivate_super+0x5c/0x60
>> [<ffffffff811e3b5f>] cleanup_mnt+0x3f/0x90
>> [<ffffffff811e3bf2>] __cleanup_mnt+0x12/0x20
>> [<ffffffff8109dad1>] task_work_run+0x81/0xa0
>> [<ffffffff810021c0>] exit_to_usermode_loop+0xb0/0xc0
>> [<ffffffff81002b44>] syscall_return_slowpath+0xd4/0x130
>> [<ffffffff8169dc0c>] int_ret_from_sys_call+0x25/0x8f
>> ---[ end trace cee6ace13018e140 ]---
>> BTRFS: space_info 4 has 18446742182612910080 free, is not full
>> BTRFS: space_info total=82678120448, used=64784695296, pinned=0,
>> reserved=0, may_use=1908990066688, readonly=0
>>
>> Greets,
>> Stefan
>>
>>> Regards,
>>> Xiaoguang Wang
>>>
>>>> Stefan
>>>>
>>>>> Regards,
>>>>> Xiaoguang Wang
>>>>>
>>>>>> I tried hard to reproduce it but i can't get it to reproduce with a
>>>>>> test
>>>>>> script. Any ideas?
>>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>> Reagrds,
>>>>>>> Xiaoguang Wang
>>>>>>>
>>>>>>>> Greets,
>>>>>>>> Stefan
>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Xiaoguang Wang
>>>>>>>>>> Greets,
>>>>>>>>>> Stefan
>>>>>>>>>> -- 
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>
>>>
>

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Holger Hoffstätte]

On 09/28/16 13:35, Wang Xiaoguang wrote:
> hello,
> 
> On 09/28/2016 07:15 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_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 and yesterday from different servers:
>> | BTRFS: space_info 4 has 18446742182612910080 free, is not full |
>> | BTRFS: space_info 4 has 18446742254739439616 free, is not full |
>> | BTRFS: space_info 4 has 18446743980225085440 free, is not full |
>> | 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-rc8 kernel
>> - use latest vanilla 4.4 kernel
>> - use latest 4.4 kernel + patches from holger hoffstaette

Was that 4.4.22? It contains a patch by Goldwyn Rodrigues called
"Prevent qgroup->reserved from going subzero" which should prevent
this from happening. This should only affect filesystems with enabled
quota; you said you didn't have quota enabled, yet some quota-only
patches caused problems on your system (despite being scheduled for
4.9 and apparently working fine everywhere else, even when I
specifically tested them *with* quota enabled).

So, long story short: something doesn't add up.

It means either:
- you tried my patchset for 4.4.21 (i.e. *without* the above patch)
  and should bump to .22 right away
- you _do_ have qgroups enabled for some reason (systemd?)
- your fs is corrupted and needs nuking
- you did something else entirely
- unknown unknowns aka. ¯\_(ツ)_/¯

There is also the chance that your use of compress-force (or rather
compression in general) causes leakage; compression runs asynchronously
and I wouldn't be surprised if that is still full of racy races..which
would be unfortunate, but you could try to disable compression for a
while and see what  happens, assuming the space requirements allow this
experiment.

You have also not told us whether this happens only on one (potentially
corrupted/confused) fs or on every one - my impression was that you have
several sharded backup filesystems/machines; not sure if that is still
the case. If it happens only on one specific fs chances are it's hosed.

> I also met enospc error in 4.8-rc6 when doing big files create and delete tests,
> for my cases, I have written some patches to fix it.
> Would you please apply my patches to have a try:
> btrfs: try to satisfy metadata requests when every flush_space() returns
> btrfs: try to write enough delalloc bytes when reclaiming metadata space
> btrfs: make shrink_delalloc() try harder to reclaim metadata space

These are all in my series for 4.4.22 and seem to work fine, however
Stefan's workload has nothing directly to do with big files; instead
it's the worst case scenario in terms of fragmentation (of huge files) and
a huge number of extents: incremental backups of VMs via rsync --inplace 
with forced compression.

IMHO this way of making backups is suboptimal in basically every possible
way, despite its convenience appeal. With such huge space requirements
it would be more effective to have a "current backup" to rsync into and
then take a snapshot (for fs consistency), pack the snapshot to a tar.gz
(massively better compression than with btrfs), dump them into your Ceph
cluster as objects with expiry (preferrably a separate EC pool) and then
immediately delete the snapshot from the local fs. That should relieve the
landing fs from getting overloaded by COWing and too many snapshots (approx.
#VMs * #versions). The obvious downside is that restoring an archived
snapshot would require some creative efforts.

Other alternatives exist, but are probably even more (too) expensive.

-h

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

Dear Holger,

first thanks for your long e-mail.

Am 28.09.2016 um 14:47 schrieb Holger Hoffstätte:
> On 09/28/16 13:35, Wang Xiaoguang wrote:
>> hello,
>>
>> On 09/28/2016 07:15 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_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 and yesterday from different servers:
>>> | BTRFS: space_info 4 has 18446742182612910080 free, is not full |
>>> | BTRFS: space_info 4 has 18446742254739439616 free, is not full |
>>> | BTRFS: space_info 4 has 18446743980225085440 free, is not full |
>>> | 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-rc8 kernel
>>> - use latest vanilla 4.4 kernel
>>> - use latest 4.4 kernel + patches from holger hoffstaette
> 
> Was that 4.4.22? It contains a patch by Goldwyn Rodrigues called
> "Prevent qgroup->reserved from going subzero" which should prevent
> this from happening. This should only affect filesystems with enabled
> quota; you said you didn't have quota enabled, yet some quota-only
> patches caused problems on your system (despite being scheduled for
> 4.9 and apparently working fine everywhere else, even when I
> specifically tested them *with* quota enabled).

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 same output on all backup machines.

> It means either:
> - you tried my patchset for 4.4.21 (i.e. *without* the above patch)
>   and should bump to .22 right away

No it's 4.4.22

> - you _do_ have qgroups enabled for some reason (systemd?)

No see above - but yes i use systemd.

> - your fs is corrupted and needs nuking

If this is the case all FS on 5 servers must be corrupted and all of
them were installed at a different date / year. The newest one just 5
month ago with kernel 4.1 the others with 3.18. Also a lot of other
systems with just 100-900GB of space are working fine.

> - you did something else entirely
No idea what this could be.

> There is also the chance that your use of compress-force (or rather
> compression in general) causes leakage; compression runs asynchronously
> and I wouldn't be surprised if that is still full of racy races..which
> would be unfortunate, but you could try to disable compression for a
> while and see what  happens, assuming the space requirements allow this
> experiment.
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 whether disabling compression fixes this.

What speaks against this is that i've also a MariaDB Server which runs
fine since two years with compress-force but uses only < 100GB files and
also does not create and remove them on a daily basis.

> You have also not told us whether this happens only on one (potentially
> corrupted/confused) fs or on every one - my impression was that you have
> several sharded backup filesystems/machines; not sure if that is still
> the case. If it happens only on one specific fs chances are it's hosed.

It happens on all of them - sorry if i missed this.

>> I also met enospc error in 4.8-rc6 when doing big files create and delete tests,
>> for my cases, I have written some patches to fix it.
>> Would you please apply my patches to have a try:
>> btrfs: try to satisfy metadata requests when every flush_space() returns
>> btrfs: try to write enough delalloc bytes when reclaiming metadata space
>> btrfs: make shrink_delalloc() try harder to reclaim metadata space
> 
> These are all in my series for 4.4.22 and seem to work fine, however
> Stefan's workload has nothing directly to do with big files; instead
> it's the worst case scenario in terms of fragmentation (of huge files) and
> a huge number of extents: incremental backups of VMs via rsync --inplace 
> with forced compression.

No that's not the case. No rsync nor inplace is involved. I'm dumping
differences directly from ceph and put them on top of a base image but
only for 7 days. So it's not endless fragmenting the file. After 7 days
a clean whole image is dumped.

 > IMHO this way of making backups is suboptimal in basically every possible
> way, despite its convenience appeal. With such huge space requirements
> it would be more effective to have a "current backup" to rsync into and
> then take a snapshot (for fs consistency), pack the snapshot to a tar.gz
> (massively better compression than with btrfs), dump them into your Ceph
> cluster as objects with expiry (preferrably a separate EC pool) and then
> immediately delete the snapshot from the local fs. That should relieve the
> landing fs from getting overloaded by COWing and too many snapshots (approx.
> #VMs * #versions). The obvious downside is that restoring an archived
> snapshot would require some creative efforts.

yes and no - this is not idea and even very slow if your customers need
backups on a daily basis. So you must be able to mount a specific backup
very fast. And stacking on demand is mostly too slow - but this is far
away from the topic in this thread.

Greets,
Stefan

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Holger Hoffstätte]

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 same output on all backup machines.

OK, that is really good to know (your other mails arrived just after I
sent mine). The fact that you see this problem with all kernels - even with
4.8rc - *and* on all machines is good (in a way) because it means I haven't
messed up anything, and we're not chasing ghosts caused by broken backport
patches.

>> would be unfortunate, but you could try to disable compression for a
>> while and see what  happens, assuming the space requirements allow this
>> experiment.
> 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 whether disabling compression fixes this.

Great. Remember to undo the compression on existing files, or create
them from scratch.

> No that's not the case. No rsync nor inplace is involved. I'm dumping
> differences directly from ceph and put them on top of a base image but
> only for 7 days. So it's not endless fragmenting the file. After 7 days
> a clean whole image is dumped.

That sounds sane but it's also not at all how you described things to me
previosuly ;) But OK. How do you "dump differences directly from
Ceph"? I'd assume the VM images are RBDs, but it sounds you're somehow
using overlayfs.

> yes and no - this is not idea and even very slow if your customers need
> backups on a daily basis. So you must be able to mount a specific backup
> very fast. And stacking on demand is mostly too slow - but this is far
> away from the topic in this thread.

I understand the desire to mount & immediately access backups - it's what
I do here at home too (every machine can access its own last #n backups
via NFS) and it's very useful.

Anyway..something is off and you successfully cause it while other
people apparently do not. Do you still use those nonstandard mount
options with extremely long transaction flush times?

-h

Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full

[Stefan Priebe - Profihost AG]

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 whether disabling compression fixes this.
> 
> Great. Remember to undo the compression on existing files, or create
> them from scratch.

I create files from scratch - but currently i can't trigger the problem
with my testscript. But even in production load it's not that easy. I
need to process 60-120 files before the error is triggered.

>> No that's not the case. No rsync nor inplace is involved. I'm dumping
>> differences directly from ceph and put them on top of a base image but
>> only for 7 days. So it's not endless fragmenting the file. After 7 days
>> a clean whole image is dumped.
> 
> That sounds sane but it's also not at all how you described things to me
> previosuly ;) But OK.
I'm sorry. May be my english is just bad, you got me wrong or was drunk
*joke*. It never changed.

> How do you "dump differences directly from
> Ceph"? I'd assume the VM images are RBDs, but it sounds you're somehow
> using overlayfs.

You can use rbd diff to export differences between two snapshots. So no
overlayfs involved.

> Anyway..something is off and you successfully cause it while other
> people apparently do not.
Sure - i know that. But i still don't want to switch to zfs.

> Do you still use those nonstandard mount
> options with extremely long transaction flush times?
No i removed commit=300 just to be sure they do not cause this issue.

Sure,
Stefan