From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfs: free space inode generation (0) did not match free space cache generation
Date: Fri, 28 Jan 2011 10:59:56 +0100 [thread overview]
Message-ID: <4D42939C.5020605@wpkg.org> (raw)
Not sure if the:
btrfs: free space inode generation (0) did not match free space cache generation
is supposed to be fixed in 2.6.38-rc2?
I'm getting such entries in dmesg:
[12638.713154] device fsid 1142843480ad2d13-4bdc742fd9b1f7b0 devid 1 transid 3501 /dev/sdb4
[12638.713528] btrfs: force zlib compression
[12638.959864] btrfs: disk space caching is enabled
[12679.397549] btrfs: free space inode generation (0) did not match free space cache generation (3491) for block group 10766778368
[12853.160162] btrfs: free space inode generation (0) did not match free space cache generation (3467) for block group 282960330752
[12853.160176] btrfs: free space inode generation (0) did not match free space cache generation (3470) for block group 285107814400
[12853.160187] btrfs: free space inode generation (0) did not match free space cache generation (3478) for block group 290476523520
[12853.160198] btrfs: free space inode generation (0) did not match free space cache generation (3480) for block group 292624007168
[12853.237298] btrfs: free space inode generation (0) did not match free space cache generation (3485) for block group 296918974464
[12853.237316] btrfs: free space inode generation (0) did not match free space cache generation (3486) for block group 299066458112
[12853.237328] btrfs: free space inode generation (0) did not match free space cache generation (3487) for block group 300140199936
[12853.237339] btrfs: free space inode generation (0) did not match free space cache generation (3488) for block group 301213941760
[12858.468374] btrfs: free space inode generation (0) did not match free space cache generation (3430) for block group 223904530432
[12858.468392] btrfs: free space inode generation (0) did not match free space cache generation (3432) for block group 226052014080
[12858.468405] btrfs: free space inode generation (0) did not match free space cache generation (3434) for block group 228199497728
[12860.040819] btrfs: free space inode generation (0) did not match free space cache generation (3420) for block group 213167112192
[12860.040836] btrfs: free space inode generation (0) did not match free space cache generation (3422) for block group 215314595840
[12860.040852] btrfs: free space inode generation (0) did not match free space cache generation (3424) for block group 217462079488
[12860.040865] btrfs: free space inode generation (0) did not match free space cache generation (3426) for block group 219609563136
[12860.040877] btrfs: free space inode generation (0) did not match free space cache generation (3428) for block group 221757046784
I saw a similar discussion in December 2010, but I'm not sure if the fix was pushed yet or not?
The filesystem should have plenty of free space free:
Filesystem Size Used Avail Use% Mounted on
/dev/sdb4 336G 156G 179G 47% /srv
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2011-01-28 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 9:59 Tomasz Chmielewski [this message]
2011-01-28 13:45 ` btrfs: free space inode generation (0) did not match free space cache generation Josef Bacik
2011-01-28 13:56 ` Tomasz Chmielewski
2011-01-28 13:57 ` 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=4D42939C.5020605@wpkg.org \
--to=mangoo@wpkg.org \
--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