From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Su Yue <suy.fnst@cn.fujitsu.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: Su Yue <Damenly_Su@gmx.com>
Subject: Re: fsck lowmem mode only: ERROR: errors found in fs roots
Date: Wed, 05 Sep 2018 14:33:44 +0200 [thread overview]
Message-ID: <37c6a0bd07091b71ead2650bc8e82a02dfffd5b3.camel@scientia.net> (raw)
In-Reply-To: <94750beb-c339-756a-11ec-f2bcc72b98e3@cn.fujitsu.com>
On Wed, 2018-09-05 at 15:04 +0800, Su Yue wrote:
> Agreed with Qu, btrfs-check shall not try to do any write.
Well.. it could have been just some coincidence :-)
> I found the errors should blame to something about inode_extref check
> in lowmem mode.
So you mean errors in btrfs-check... and it was a false positive?
> I have writeen three patches to detect and report errors about
> inode_extref. For your convenience, it's based on v4.17:
> https://github.com/Damenly/btrfs-progs/tree/ext_ref_v4.17
I hope I can test them soon.... could take a bit longer as I'm about to
head off into vacation.
Cheers,
Chris.
next prev parent reply other threads:[~2018-09-05 17:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 16:47 fsck lowmem mode only: ERROR: errors found in fs roots Christoph Anton Mitterer
2018-08-31 2:33 ` Su Yue
2018-09-03 20:24 ` Christoph Anton Mitterer
2018-09-04 9:14 ` Qu Wenruo
2018-09-04 11:45 ` Christoph Anton Mitterer
2018-09-05 7:04 ` Su Yue
2018-09-05 12:33 ` Christoph Anton Mitterer [this message]
2018-09-05 12:43 ` Su Yue
2018-10-18 14:41 ` Christoph Anton Mitterer
2018-10-19 1:11 ` Su Yue
2018-10-19 1:13 ` Su Yue
2018-10-27 12:15 ` Christoph Anton Mitterer
2018-11-02 14:10 ` Christoph Anton Mitterer
2018-11-03 1:34 ` Su Yue
2018-11-03 1:38 ` Christoph Anton Mitterer
2018-11-03 9:20 ` Nikolay Borisov
2018-11-05 1:21 ` Su Yue
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=37c6a0bd07091b71ead2650bc8e82a02dfffd5b3.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=Damenly_Su@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=suy.fnst@cn.fujitsu.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).