linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrik Lundquist <patrik.lundquist@gmail.com>
To: Ivan P <chrnosphered@gmail.com>
Cc: btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: scrub: Tree block spanning stripes, ignored
Date: Thu, 7 Apr 2016 17:46:05 +0200	[thread overview]
Message-ID: <CAA7pwKPENs_xaw9M2=BWzPxcVP4TzML225BxwnSHiAPupSzrKQ@mail.gmail.com> (raw)
In-Reply-To: <CADzmB21RH8HOHzAvCrD1ueSy-abT-J=-XAhn6yrQPW6USA1EQg@mail.gmail.com>

On 7 April 2016 at 17:33, Ivan P <chrnosphered@gmail.com> wrote:
>
> After running btrfsck --readonly again, the output is:
>
> ===============================
> Checking filesystem on /dev/sdb
> UUID: 013cda95-8aab-4cb2-acdd-2f0f78036e02
> checking extents
> checking free space cache
> block group 632463294464 has wrong amount of free space
> failed to load free space cache for block group 632463294464

Mount once with option "clear_cache" and check again.

  reply	other threads:[~2016-04-07 15:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-02 16:29 scrub: Tree block spanning stripes, ignored Ivan P
2016-04-03  1:24 ` Qu Wenruo
2016-04-06 19:39   ` Ivan P
2016-04-07  0:58     ` Qu Wenruo
2016-04-07 15:33       ` Ivan P
2016-04-07 15:46         ` Patrik Lundquist [this message]
2016-04-08  0:23         ` Qu Wenruo
2016-04-09  9:53           ` Ivan P
2016-04-11  1:10             ` Qu Wenruo
2016-04-12 17:15               ` Ivan P
2016-05-06 11:25                 ` Ivan P
2016-05-09  1:28                   ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
2016-03-25 14:16 Ivan P
2016-03-27  9:54 ` Ivan P
2016-03-27  9:56   ` Ivan P
2016-03-27 14:23   ` Qu Wenruo
     [not found]     ` <CADzmB20uJmLgMSgHX1vse35Ssj0rKXxzsTTum+L2ZnjFaBCrww@mail.gmail.com>
2016-03-28  1:10       ` Qu Wenruo
2016-03-28 21:21         ` Ivan P
2016-03-29  1:57           ` Qu Wenruo

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='CAA7pwKPENs_xaw9M2=BWzPxcVP4TzML225BxwnSHiAPupSzrKQ@mail.gmail.com' \
    --to=patrik.lundquist@gmail.com \
    --cc=chrnosphered@gmail.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).