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: Thu, 29 Sep 2016 15:13:17 +0800 [thread overview]
Message-ID: <57ECBF0D.3050609@cn.fujitsu.com> (raw)
In-Reply-To: <0e556b63-7c85-1e97-00b0-91bfca44e82c@profihost.ag>
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
>>>>>>>
>>>>>>>
>>>>
>>
>>
>
next prev parent reply other threads:[~2016-09-29 7:18 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 [this message]
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
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=57ECBF0D.3050609@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).