From: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS: space_info 4 has 18446742286429913088 free, is not full
Date: Tue, 11 Oct 2016 11:16:12 +0800 [thread overview]
Message-ID: <57FC597C.3040606@cn.fujitsu.com> (raw)
In-Reply-To: <c3318651-b339-032a-8471-40bd97398a27@profihost.ag>
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
>>>>>>>>>>>
>>>>>>>>>>>
>>>>
>>
>>
>
next prev parent reply other threads:[~2016-10-11 3:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 11:15 BTRFS: space_info 4 has 18446742286429913088 free, is not full Stefan Priebe - Profihost AG
2016-09-28 11:35 ` Wang Xiaoguang
2016-09-28 12:02 ` Stefan Priebe - Profihost AG
2016-09-28 12:10 ` Wang Xiaoguang
2016-09-28 12:25 ` Stefan Priebe - Profihost AG
2016-09-29 6:49 ` Stefan Priebe - Profihost AG
2016-09-29 6:55 ` Wang Xiaoguang
2016-09-29 7:09 ` Stefan Priebe - Profihost AG
2016-09-29 7:13 ` Wang Xiaoguang
2016-09-29 7:27 ` Stefan Priebe - Profihost AG
2016-09-29 10:03 ` Adam Borowski
2016-09-29 10:05 ` Stefan Priebe - Profihost AG
2016-10-06 3:04 ` Wang Xiaoguang
2016-10-06 7:32 ` Stefan Priebe - Profihost AG
2016-10-06 7:35 ` Stefan Priebe - Profihost AG
2016-10-07 7:03 ` Stefan Priebe - Profihost AG
2016-10-07 7:17 ` Wang Xiaoguang
2016-10-07 7:47 ` Paul Jones
2016-10-07 7:48 ` Paul Jones
2016-10-07 7:59 ` Stefan Priebe - Profihost AG
2016-10-07 8:05 ` Stefan Priebe - Profihost AG
2016-10-07 8:06 ` Stefan Priebe - Profihost AG
2016-10-07 8:07 ` Wang Xiaoguang
2016-10-07 8:16 ` Stefan Priebe - Profihost AG
2016-10-07 8:19 ` Wang Xiaoguang
2016-10-07 9:33 ` Holger Hoffstätte
2016-10-08 5:56 ` Stefan Priebe - Profihost AG
2016-10-08 20:49 ` Stefan Priebe - Profihost AG
2016-10-08 6:05 ` Stefan Priebe - Profihost AG
2016-10-10 20:06 ` Stefan Priebe - Profihost AG
2016-10-11 3:16 ` Wang Xiaoguang [this message]
2016-10-23 17:47 ` Stefan Priebe - Profihost AG
2016-10-25 10:48 ` Wang Xiaoguang
2016-09-28 12:47 ` Holger Hoffstätte
2016-09-28 13:06 ` Stefan Priebe - Profihost AG
2016-09-28 13:44 ` Holger Hoffstätte
2016-09-28 13:59 ` Stefan Priebe - Profihost AG
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57FC597C.3040606@cn.fujitsu.com \
--to=wangxg.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).