From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Cc: chris@colorremedies.com, dsterba@suse.cz
Subject: Re: [PATCH 0/9] Lowmem mode fsck fixes with fsck-tests framework update
Date: Wed, 25 Jan 2017 05:40:11 +0100 [thread overview]
Message-ID: <1485319211.12065.15.camel@scientia.net> (raw)
In-Reply-To: <8d21a04e-7035-5b5d-5b58-9ac0d7f93f02@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On Wed, 2017-01-25 at 12:16 +0800, Qu Wenruo wrote:
> New patches are out now.
>
> Although I just updated
> 0001-btrfs-progs-lowmem-check-Fix-wrong-block-group-check.patch to
> fix
> all similar bugs.
>
> You could get it from github:
> https://github.com/adam900710/btrfs-progs/tree/lowmem_fixes
Sure, will take a while, though (hopefully get it done tomorrow)
> Unfortunately, I didn't find the cause of the remaining error of
> that
> missing csum.
> And considering the size of your fs, btrfs-image is not possible, so
> I'm
> afraid you need to test the patches every time it updates.
No worries :-)
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2017-01-25 4:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 9:13 [PATCH 0/9] Lowmem mode fsck fixes with fsck-tests framework update Qu Wenruo
2017-01-23 9:13 ` [PATCH 1/9] btrfs-progs: lowmem check: Fix wrong block group check when search slot points to slot beyong leaf Qu Wenruo
2017-01-23 9:13 ` [PATCH 2/9] btrfs-progs: fsck-test: Add test image for lowmem mode block group false alert Qu Wenruo
2017-01-23 9:13 ` [PATCH 3/9] btrfs-progs: fsck: Output verbose error when fsck found a bug Qu Wenruo
2017-01-23 9:13 ` [PATCH 4/9] btrfs-progs: lowmem check: Fix false alert in checking data extent pointing to prealloc extent Qu Wenruo
2017-01-23 9:13 ` [PATCH 5/9] btrfs-progs: lowmem check: Fix extent item size false alert Qu Wenruo
2017-01-23 9:13 ` [PATCH 6/9] btrfs-progs: tests: Move fsck-tests/015 to fuzz tests Qu Wenruo
2017-01-23 9:13 ` [PATCH 7/9] btrfs-progs: fsck-tests: Make 013 compatible with lowmem mode Qu Wenruo
2017-01-23 9:13 ` [PATCH 8/8] btrfs-progs: fsck: Fix lowmem mode override to allow it skip repair work Qu Wenruo
2017-01-23 9:13 ` [PATCH 8/9] btrfs-progs: fsck-tests: Add new test case for partly written prealloc extent Qu Wenruo
2017-01-23 9:13 ` [PATCH 9/9] btrfs-progs: fsck: Fix lowmem mode override to allow it skip repair work Qu Wenruo
2017-01-24 16:54 ` [PATCH 0/9] Lowmem mode fsck fixes with fsck-tests framework update Christoph Anton Mitterer
2017-01-25 0:44 ` Qu Wenruo
2017-01-25 0:46 ` Christoph Anton Mitterer
2017-01-25 4:16 ` Qu Wenruo
2017-01-25 4:40 ` Christoph Anton Mitterer [this message]
2017-01-26 2:50 ` Christoph Anton Mitterer
2017-01-26 3:10 ` Qu Wenruo
2017-01-26 3:30 ` Christoph Anton Mitterer
2017-01-26 23:31 ` Christoph Anton Mitterer
2017-01-29 4:27 ` Qu Wenruo
2017-01-30 3:07 ` Christoph Anton Mitterer
2017-02-01 1:06 ` Qu Wenruo
2017-02-01 22:03 ` Christoph Anton Mitterer
2017-02-02 0:25 ` Qu Wenruo
2017-02-02 2:12 ` Qu Wenruo
[not found] ` <1486098502.7443.3.camel@lmu.de>
2017-02-03 6:20 ` Qu Wenruo
2017-02-03 23:01 ` Christoph Anton Mitterer
2017-02-06 1:25 ` 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=1485319211.12065.15.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=chris@colorremedies.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.