From: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: disk space caching generation missmatch
Date: Wed, 1 Dec 2010 17:46:14 +0100 [thread overview]
Message-ID: <201012011746.14458.johannes.hirte@fem.tu-ilmenau.de> (raw)
After enabling disk space caching I've observed several log entries like this:
btrfs: free space inode generation (0) did not match free space cache generation (169594) for block group 15464398848
I'm not sure, but it seems this happens on every reboot. Is this something to
worry about?
regards,
Johannes
next reply other threads:[~2010-12-01 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 16:46 Johannes Hirte [this message]
2010-12-01 17:40 ` disk space caching generation missmatch Josef Bacik
2010-12-01 19:56 ` Johannes Hirte
2010-12-01 20:03 ` Josef Bacik
2010-12-01 21:22 ` Johannes Hirte
2010-12-01 21:40 ` Johannes Hirte
2010-12-02 20:34 ` Josef Bacik
2010-12-02 21:45 ` C Anthony Risinger
2010-12-03 0:07 ` Johannes Hirte
2010-12-03 0:44 ` C Anthony Risinger
2010-12-03 0:57 ` Johannes Hirte
2010-12-03 18:14 ` Josef Bacik
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=201012011746.14458.johannes.hirte@fem.tu-ilmenau.de \
--to=johannes.hirte@fem.tu-ilmenau.de \
--cc=josef@redhat.com \
--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 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).