linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: [bug] btrfs check clear-space-cache v1 corrupted file system
Date: Fri, 1 Mar 2019 17:20:00 -0700	[thread overview]
Message-ID: <CAJCQCtQrLLpX8uZwp2BYfgaF1QPfuf1_XRjVxG24cbDHfEo2uA@mail.gmail.com> (raw)

Problem happens with btrfsprogs 4.19.1

https://bugzilla.kernel.org/show_bug.cgi?id=202717

That bug report includes the trace in user space; but I've also
processed the resulting coredump file with gdb and attached that to
the bug report.

Before using --clear-space-cache v1, btrfs scrub and btrfs check came
up clean no errors. Following the crash, I compiled brfsprogs 4.20.2
and ran 'btrfs check' which finds corruption.

I've taken no further action, and the btrfs check output gives me no
useful plain language information what the next steps are. So I'm just
gonna leave it alone since it's a backup volume anyway.



-- 
Chris Murphy

             reply	other threads:[~2019-03-02  0:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02  0:20 Chris Murphy [this message]
2019-03-02  1:05 ` [bug] btrfs check clear-space-cache v1 corrupted file system Qu Wenruo
2019-03-02  2:29   ` Chris Murphy
2019-03-02  2:54     ` Chris Murphy
     [not found]       ` <CAJCQCtQaQ0XFUGFdWfgwmTSPTUShrZgXmsh55c-reS9iS+WpFg@mail.gmail.com>
2019-03-02  3:22         ` Chris Murphy
2019-03-02  4:14     ` Qu Wenruo
     [not found]       ` <CAJCQCtRyStqPLOXHVWkcha3GkA7wt2u00qSH7DfUyL_ift5ppQ@mail.gmail.com>
2019-03-10 23:20         ` Chris Murphy
2019-08-12  4:24           ` Chris Murphy
2019-08-12  4:54             ` Qu Wenruo
2019-08-12  5:04               ` Chris Murphy

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=CAJCQCtQrLLpX8uZwp2BYfgaF1QPfuf1_XRjVxG24cbDHfEo2uA@mail.gmail.com \
    --to=lists@colorremedies.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).