From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: Jannik Winkel <j.winkel@profihost.ag>
Subject: Re: ENOSPC / no space on very large devices
Date: Wed, 20 Jul 2016 09:35:32 +0200 [thread overview]
Message-ID: <578F29C4.9030808@applied-asynchrony.com> (raw)
In-Reply-To: <1659eb11-0025-d9d4-c590-2a4d721bb299@profihost.ag>
On 07/20/16 07:31, Stefan Priebe - Profihost AG wrote:
> Hi list,
>
> while i didn't had the problem for some month i'm now getting ENOSPC on
> a regular basis on one host.
Well, it's getting better. :)
> if i umount the volume i get traces (i already did a clear_cache 4 days
> ago to recalculate the space_tree):
>
> [545031.675797] ------------[ cut here ]------------
> [545031.725166] WARNING: CPU: 1 PID: 17711 at
> fs/btrfs/extent-tree.c:5710 btrfs_free_block_groups+0x35a/0x400 [btrfs]()
This is "only" a warning, but as we can see below it indicates a real
problem. The warning was added only recently to for-next by the patch called
"Btrfs: warn_on for unaccounted spaces" [1], but I've had it in my tree
forever. Never seen the warning myself.
(snip)
> [545037.909700] BTRFS: space_info 4 has 18446743523026157568 free, is
> not full
Wow, ~18.4 exabytes really is a lot of free space. :)
So it looks like something underflowed the space_info and now things are
confused for about ~550 GB. Unfortunately I have no good idea how to fix
that. :(
> The kernel is something special - i'm using this one from holger:
> https://github.com/hhoffstaette/kernel-patches
>
> which is basically a 4.4.15 + several patches especially a lot of btrfs
> patches up to 4.8 i think.
More like for-next with all the pagesize/sectorsize stuff carefully
avoided. I'm really looking forward to 4.8, this is becoming unwieldy..
-h
[1] https://git.kernel.org/cgit/linux/kernel/git/kdave/linux.git/commit/?h=for-next&id=d555b6c380c644af63dbdaa7cc14bba041a4e4dd
next prev parent reply other threads:[~2016-07-20 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 5:31 ENOSPC / no space on very large devices Stefan Priebe - Profihost AG
2016-07-20 6:31 ` Wang Xiaoguang
2016-07-29 5:42 ` Stefan Priebe - Profihost AG
2016-07-20 7:35 ` Holger Hoffstätte [this message]
2016-07-29 5:44 ` 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=578F29C4.9030808@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=j.winkel@profihost.ag \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.