From: Omar Sandoval <osandov@osandov.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Josef Bacik <jbacik@fb.com>
Subject: Re: memory overflow or undeflow in free space tree / space_info?
Date: Fri, 29 Jul 2016 12:14:59 -0700 [thread overview]
Message-ID: <20160729191459.GB28505@vader> (raw)
In-Reply-To: <20160729191153.GA28505@vader>
On Fri, Jul 29, 2016 at 12:11:53PM -0700, Omar Sandoval wrote:
> On Fri, Jul 29, 2016 at 08:40:26PM +0200, Stefan Priebe - Profihost AG wrote:
> > Dear list,
> >
> > i'm seeing btrfs no space messages frequently on big filesystems (> 30TB).
> >
> > In all cases i'm getting a trace like this one a space_info warning.
> > (since commit [1]). Could someone please be so kind and help me
> > debugging / fixing this bug? I'm using space_cache=v2 on all those systems.
>
> Hm, so I think this indicates a bug in space accounting somewhere else
> rather than the free space tree itself. I haven't debugged one of these
> issues before, I'll see if I can reproduce it. Cc'ing Josef, too.
I should've asked, what sort of filesystem activity triggers this?
--
Omar
next prev parent reply other threads:[~2016-07-29 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 18:40 memory overflow or undeflow in free space tree / space_info? Stefan Priebe - Profihost AG
2016-07-29 19:11 ` Omar Sandoval
2016-07-29 19:14 ` Omar Sandoval [this message]
2016-07-29 19:40 ` Stefan Priebe - Profihost AG
2016-07-29 21:03 ` Josef Bacik
2016-07-29 22:57 ` Holger Hoffstätte
2016-07-29 23:09 ` Holger Hoffstätte
2016-08-04 11:40 ` Stefan Priebe - Profihost AG
2016-08-08 6:17 ` Stefan Priebe - Profihost AG
2016-08-10 21:31 ` Stefan Priebe - Profihost AG
2016-08-11 6:09 ` Stefan Priebe - Profihost AG
2016-08-14 15:22 ` Stefan Priebe - Profihost AG
2016-08-29 14:02 ` Stefan Priebe - Profihost AG
2016-07-29 19:39 ` 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=20160729191459.GB28505@vader \
--to=osandov@osandov.com \
--cc=jbacik@fb.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).