From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs: free space inode generation (0) did not match free space cache generation
Date: Fri, 28 Jan 2011 14:56:24 +0100 [thread overview]
Message-ID: <4D42CB08.5030904@wpkg.org> (raw)
In-Reply-To: <20110128134531.GB4884@dhcp231-156.rdu.redhat.com>
On 28.01.2011 14:45, Josef Bacik wrote:
> It's not a problem, it just means that the cache is being discarded, which is
> what is supposed to happen. You probably ran out of space or one of the other
> corner cases where we can't write out the space cache. Thanks,
FYI, there is plenty of free space (~150 GB).
It could be some corner case:
- filesystem is mounted with compress-force,
- one kvm process (the only writer to btrfs) writes to the btrfs
filesystem, via the virtual guest using a 220 GB qcow2 image file (lots
of writes) and a 7 GB qcow2 image file (very few writes).
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2011-01-28 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 9:59 btrfs: free space inode generation (0) did not match free space cache generation Tomasz Chmielewski
2011-01-28 13:45 ` Josef Bacik
2011-01-28 13:56 ` Tomasz Chmielewski [this message]
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=4D42CB08.5030904@wpkg.org \
--to=mangoo@wpkg.org \
--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