From: yzb3@wp.pl
To: "linux-btrfs" <linux-btrfs@vger.kernel.org>
Subject: RE: BTRFS error after clearing cache
Date: Thu, 14 Nov 2013 14:49:36 +0100 [thread overview]
Message-ID: <5284d4f01340e9.50736959@wp.pl> (raw)
>Hello,
>I wanted to make sure that my boot slowdown was related to space_cache so I rebooted the PC several times and
>it did become slower again. What is more, it doesn't seem like I even need to generate any actual IO traffic
>to trigger this.
>I thought I might give clear_cache a shot again and to test the boot speed with nospace_cache as well. After
>first booting with clear_cache,nospace_cache and nospace_cache afterwards I was unhappy about the
>boot speed, so I decided to clear the nospace_cache argument so that the cache would be rebuilt. However,
>even though my boot speed did improve (not well enough, though), I received 2 errors (this is also the
>output of dmesg | grep BTRFS):
>[ 5.528707] BTRFS error (device sda2): block group 1103101952 has wrong amount of free space
>[ 5.529630] BTRFS error (device sda2): failed to load free space cache for block group 1103101952
>It comes up after every reboot now. The output of dmesg | grep trfs (no 'b', because it is inconsistent) is:
>[ 1.225343] Btrfs loaded
>[ 1.245586] btrfs: disk space caching is enabled
>[ 1.245588] btrfs: has skinny extents
>Any ideas on how I can remove this error? This doesn't break my boot or anything, but it probably slows things
>down, leaves some fs garbage etc. By the way, it would be a good idea to be able to search for a consistent
>value in dmesg.
This is still present under kernel 12.0; during a boot with clear_cache the messages are gone, but right after removing
this option (so that the cache is rebuilt) they appear again.
next reply other threads:[~2013-11-14 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 13:49 yzb3 [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-10 16:15 BTRFS error after clearing cache yzb3
2013-11-10 16:48 ` Duncan
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=5284d4f01340e9.50736959@wp.pl \
--to=yzb3@wp.pl \
--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.