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 majord...@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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to