From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christian Pernegger <pernegger@gmail.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 22:06:52 +0800 [thread overview]
Message-ID: <0d48803b-b8f0-2ab7-dade-d92067b91202@gmx.com> (raw)
In-Reply-To: <CAKbQEqGOJjNAFMitAU=coVboaat9pi5b-6DxFg4SOON+6bfJ0g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1454 bytes --]
On 2019/10/26 下午9:52, Christian Pernegger wrote:
> Am Sa., 26. Okt. 2019 um 11:41 Uhr schrieb Qu Wenruo <quwenruo.btrfs@gmx.com>:
>> Thus I put a log tree check in skipbg mount option, and if it detects
>> log tree, it refuse to mount and output kernel message to require
>> nologreplay.
>
> No, it doesn't, it asks for notreelog (quoted from a few e-mails back):
Exposed a bug!
My bad!
>
>>> [ 1350.402586] BTRFS info (device dm-1): skip mount time block group searching
>>> [ 1350.402588] BTRFS info (device dm-1): disk space caching is enabled
>>> [ 1350.402589] BTRFS info (device dm-1): has skinny extents
>>> [ 1350.402590] BTRFS error (device dm-1): skip_bg must be used with
>>> notreelog mount option for dirty log
>>> [ 1350.419849] BTRFS error (device dm-1): open_ctree failed
>>>
>>> Fine by me, let's add "notreelog" as well. Note that "skip_bg" is
>>> actually written with an underscore above.
>
>> Then you can try btrfs-mod-sb, [...]
>
> Yep, that did the trick. Can mount the fs ro now, access files and it
> even reports checksum errors for a couple of them. Promising.
Mind to share the csum error log?
As you may already find out, certain CRC32 means all zero, and can
indicate more trim error for data.
Otherwise, indeed looks promising.
I'll fix the bug and update the patchset.
(Maybe also make btrfs falls back to skipbg by default)
Thanks,
Qu
>
> Cheers,
> C.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-26 14:07 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 [this message]
2019-10-26 16:30 ` Christian Pernegger
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=0d48803b-b8f0-2ab7-dade-d92067b91202@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pernegger@gmail.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