All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS warning (device sda7): block group 181491728384 has wrong amount of free space
Date: Tue, 2 May 2017 11:54:30 +0000 (UTC)	[thread overview]
Message-ID: <pan$28804$b4e53a6$f8693243$cefcb283@cox.net> (raw)
In-Reply-To: c73f374d-5d53-c2cf-d09c-5d91f0919b12@rqc.ru

Marat Khalili posted on Tue, 02 May 2017 09:14:12 +0300 as excerpted:

> I cannot understand two messages in syslog, could someone please shed
> some light? Here they are:
> 
>> Apr 29 08:54:03 container-name kernel: [792742.662375] BTRFS warning
>> (device sda7): block group 181491728384 has wrong amount of free space

>> Apr 29 08:54:03 container-name kernel: [792742.662381] BTRFS warning
>> (device sda7): failed to load free space cache for block group
>> 181491728384, rebuilding it now

> Especially strange is the fact that messages appear in LXC container's
> syslog, but not in syslog of a host system. I only saw network and
> apparmor-related messages in container syslogs before.
> 
> I didn't run any usermode btrfs tools at the time (especially in
> container, since they are not even installed there), but there's a quota
> set for this subvolume, and it was coming close to exhausting by large
> mysql database. There're no snapshots this time. smartmon finds no
> problems.

These aren't anything to be alarmed about in themselves; they're just low 
priority warnings from the free-space *cache*, saying it somehow got out 
of sync with what's actually there.  As that's just a cache, designed to 
help speed up looking for free space without having to actually go and 
check every time, and problems will be caught and that block-group's 
cache invalidated and recreated (with those messages indicating that's 
exactly what's happening) if btrfs finds there's actually data written in 
a block that the cache said was free, no harm done.

Inconsistencies are typically generated in an unclean unmount situation, 
but may not be caught until sometime later, when btrfs goes to actually 
use some space the cache says should be available, that actually isn't.

AFAIK (I'm a btrfs user and list regular, not a dev), it shouldn't have 
anything to do with quota.

I wouldn't worry about it myself, particularly if I hadn't been able to 
do a clean unmount at some point, tho if I saw the warning, I'd probably 
do a btrfs scrub just to be sure that warning wasn't hinting at some more 
real problem somewhere.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


      reply	other threads:[~2017-05-02 11:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  6:14 BTRFS warning (device sda7): block group 181491728384 has wrong amount of free space Marat Khalili
2017-05-02 11:54 ` Duncan [this message]

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='pan$28804$b4e53a6$f8693243$cefcb283@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /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.