linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: waxhead <waxhead@dirtcellar.net>
To: Hendrik Friedel <hendrik@friedels.name>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: the free space cache file is invalid, skip it
Date: Sun, 15 Mar 2020 16:49:00 +0100	[thread overview]
Message-ID: <f2e7a222-0f92-a905-bd9c-6a8d1a5a0cd1@dirtcellar.net> (raw)
In-Reply-To: <emfc09a7c5-74d2-4f64-92cc-9a8cffa964e1@ryzen>

First , I am just a regular btrfs user so take what I say with a grain 
of salt.

However, according to the FAQ here:
https://btrfs.wiki.kernel.org/index.php/FAQ

You should run btrfs check on your filfeystem. This may be a brilliant 
or horrific idea. You probably want to drop your free space cache file 
as well ,but wait until a developer answers if you wanna be on the safe 
side.

If you expect some serious help you should probably post the outputs of 
these commands and state just for the record what distro you are using 
and I am sure you will get help soon (the BTRFS list is very friendly).

uname -a
btrfs --version
btrfs filesystem show /mountpoint
btrfs filesystem usage -T /mountpoint

Hendrik Friedel wrote:
> Hello,
> 
> I see these errors in my syslog:
> 
> Mar 15 00:16:31 homeserver kernel: [524589.677551] BTRFS info (device 
> sdf1): the free space cache file (12785106812928) is invalid, skip it
> Mar 15 00:16:32 homeserver kernel: [524590.494705] BTRFS info (device 
> sdf1): the free space cache file (12787254296576) is invalid, skip it
> Mar 15 00:16:53 homeserver kernel: [524611.371823] BTRFS info (device 
> sdf1): the free space cache file (14405383225344) is invalid, skip it
> Mar 15 00:18:18 homeserver kernel: [524696.803108] BTRFS info (device 
> sdf1): the free space cache file (15598377500672) is invalid, skip it
> Mar 15 00:18:18 homeserver kernel: [524696.935340] BTRFS info (device 
> sdf1): the free space cache file (15613409886208) is invalid, skip it
> Mar 15 00:18:19 homeserver kernel: [524698.074946] BTRFS info (device 
> sdf1): the free space cache file (15643474657280) is invalid, skip it
> Mar 15 00:18:19 homeserver kernel: [524698.074952] BTRFS info (device 
> sdf1): the free space cache file (15643474657280) is invalid, skip it
> Mar 15 00:18:21 homeserver kernel: [524699.353843] BTRFS info (device 
> sdf1): the free space cache file (15663875751936) is invalid, skip it
> Mar 15 00:19:37 homeserver kernel: [524776.142963] BTRFS info (device 
> sdf1): the free space cache file (15062513221632) is invalid, skip it
> Mar 15 00:19:38 homeserver kernel: [524776.307788] BTRFS info (device 
> sdf1): the free space cache file (15065734447104) is invalid, skip it
> Mar 15 00:19:38 homeserver kernel: [524776.549028] BTRFS info (device 
> sdf1): the free space cache file (15070029414400) is invalid, skip it
> Mar 15 00:19:38 homeserver kernel: [524776.675084] BTRFS info (device 
> sdf1): the free space cache file (15071103156224) is invalid, skip it
> Mar 15 00:19:38 homeserver kernel: [524777.004195] BTRFS info (device 
> sdf1): the free space cache file (15076471865344) is invalid, skip it
> Mar 15 00:19:50 homeserver kernel: [524788.446974] BTRFS info (device 
> sdf1): the free space cache file (15559722795008) is invalid, skip it
> Mar 15 00:19:51 homeserver kernel: [524789.965874] BTRFS info (device 
> sdf1): the free space cache file (15570460213248) is invalid, skip it
> Mar 15 00:21:59 homeserver kernel: [524918.102725] BTRFS info (device 
> sdf1): the free space cache file (15064660705280) is invalid, skip it
> Mar 15 00:25:49 homeserver kernel: [525147.576735] BTRFS info (device 
> sdf1): the free space cache file (15564017762304) is invalid, skip it
> Mar 15 00:27:33 homeserver kernel: [525251.725178] BTRFS info (device 
> sdf1): the free space cache file (16411300724736) is invalid, skip it
> 
> a scrub of that drive was finde.
> Also, the stats look good:
> btrfs dev stats /srv/dev-disk-by-label-DataPool1
> [/dev/sdf1].write_io_errs    0
> [/dev/sdf1].read_io_errs     0
> [/dev/sdf1].flush_io_errs    0
> [/dev/sdf1].corruption_errs  0
> [/dev/sdf1].generation_errs  0
> [/dev/sdc1].write_io_errs    0
> [/dev/sdc1].read_io_errs     0
> [/dev/sdc1].flush_io_errs    0
> [/dev/sdc1].corruption_errs  0
> [/dev/sdc1].generation_errs  0
> 
> Is this concerning?
> What should I do?
> 
> Regards,
> Hendrik
> 

  reply	other threads:[~2020-03-15 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 14:52 the free space cache file is invalid, skip it Hendrik Friedel
2020-03-15 15:49 ` waxhead [this message]
2020-03-16  6:59   ` Re[2]: " Hendrik Friedel
2020-03-16 17:22     ` Andrei Borzenkov

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=f2e7a222-0f92-a905-bd9c-6a8d1a5a0cd1@dirtcellar.net \
    --to=waxhead@dirtcellar.net \
    --cc=hendrik@friedels.name \
    --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).