From: Christian Pernegger <pernegger@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: first it froze, now the (btrfs) root fs won't mount ...
Date: Sat, 26 Oct 2019 18:30:49 +0200 [thread overview]
Message-ID: <CAKbQEqFccH9=WsGy23CcCu-KSVWYrwffF6faRADH3oauJhgkdA@mail.gmail.com> (raw)
In-Reply-To: <0d48803b-b8f0-2ab7-dade-d92067b91202@gmx.com>
Am Sa., 26. Okt. 2019 um 16:07 Uhr schrieb Qu Wenruo <quwenruo.btrfs@gmx.com>:
> Mind to share the csum error log?
Certainly. That is, you're welcome to it, if you tell me how to
generate such a thing. Is there an elegant way to walk the entire
filesystem, trigger csum calculations for everything and generate a
log? Something like a poor man's read-only scrub?
> I'll fix the bug and update the patchset.
> (Maybe also make btrfs falls back to skipbg by default)
I appreciate it.
Cheers,
C.
next prev parent reply other threads:[~2019-10-26 16:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKbQEqE7xN1q3byFL7-_pD=_pGJ0Vm9pj7d-g+rRgtONeH-GrA@mail.gmail.com>
2019-10-19 22:34 ` first it froze, now the (btrfs) root fs won't mount Christian Pernegger
2019-10-20 0:38 ` Qu Wenruo
2019-10-20 10:11 ` Christian Pernegger
2019-10-20 10:22 ` Christian Pernegger
2019-10-20 10:28 ` Qu Wenruo
2019-10-21 10:47 ` Christian Pernegger
2019-10-21 10:55 ` Qu Wenruo
2019-10-21 11:47 ` Austin S. Hemmelgarn
2019-10-21 13:02 ` Christian Pernegger
2019-10-21 13:34 ` Qu Wenruo
2019-10-22 22:56 ` Christian Pernegger
2019-10-23 0:25 ` Qu Wenruo
2019-10-23 11:31 ` Austin S. Hemmelgarn
2019-10-24 10:41 ` Christian Pernegger
2019-10-24 11:26 ` Qu Wenruo
2019-10-24 11:40 ` Austin S. Hemmelgarn
2019-10-25 16:43 ` Christian Pernegger
2019-10-25 17:05 ` Christian Pernegger
2019-10-25 17:16 ` Austin S. Hemmelgarn
2019-10-25 17:12 ` Austin S. Hemmelgarn
2019-10-26 0:01 ` Qu Wenruo
2019-10-26 9:23 ` Christian Pernegger
2019-10-26 9:41 ` Qu Wenruo
2019-10-26 13:52 ` Christian Pernegger
2019-10-26 14:06 ` Qu Wenruo
2019-10-26 16:30 ` Christian Pernegger [this message]
2019-10-27 0:46 ` Qu Wenruo
[not found] ` <CAKbQEqFne8eohE3gvCMm8LqA-KimFrwwvE5pUBTn-h-VBhJq1A@mail.gmail.com>
2019-10-27 13:38 ` Qu Wenruo
2019-10-21 14:02 ` Austin S. Hemmelgarn
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='CAKbQEqFccH9=WsGy23CcCu-KSVWYrwffF6faRADH3oauJhgkdA@mail.gmail.com' \
--to=pernegger@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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).