From: David Sterba <dsterba@suse.cz>
To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Subject: Re: [PATCH 00/13] btrfs-progs: check: check fs roots in low_memory mode
Date: Fri, 19 Aug 2016 12:31:31 +0200 [thread overview]
Message-ID: <20160819103130.GF16983@suse.cz> (raw)
In-Reply-To: <57B6D818.5020501@cn.fujitsu.com>
On Fri, Aug 19, 2016 at 05:57:44PM +0800, Wang Xiaoguang wrote:
> Hi
>
> On 08/18/2016 01:00 AM, David Sterba wrote:
> > On Thu, Jul 28, 2016 at 03:08:12PM +0800, Lu Fengqi wrote:
> >> This patchset implements check fs trees in low memory mode, and fix the
> >> return value bug of the function cmd_check().
> >>
> >> Lu Fengqi (13):
> >> btrfs-progs: move btrfs_extref_hash() to hash.h
> >> btrfs-progs: check: introduce function to find dir_item
> >> btrfs-progs: check: introduce function to check inode_ref
> >> btrfs-progs: check: introduce function to check inode_extref
> >> btrfs-progs: check: introduce function to find inode_ref
> >> btrfs-progs: check: introduce a function to check dir_item
> >> btrfs-progs: check: introduce function to check file extent
> >> btrfs-progs: check: introduce function to check inode item
> >> btrfs-progs: check: introduce function to check fs root
> >> btrfs-progs: check: introduce function to check root ref
> >> btrfs-progs: check: introduce low_memory mode fs_tree check
> >> btrfs-progs: check: fix the return value bug of cmd_check()
> >> btrfs-progs: check: fix false warning for check_extent_item()
> > FYI, I'm going to promote this series within devel and schedule it for
> > the next release. The preparatory subset will be merged, but I might do
> > some modificaions to the command line interface.
> In current low memory fs trees check, it dose not check whether
> node or leaf is shared, which will casue btrfsck much slower when
> fs has one or more snapshots. I have prepared a patch to improve
> this issue, if you have some free time, please check it, thanks.
The low-memory mode has an experimental status (and thus is not on by
default) so the improvements are welcome of course.
prev parent reply other threads:[~2016-08-19 10:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 7:08 [PATCH 00/13] btrfs-progs: check: check fs roots in low_memory mode Lu Fengqi
2016-07-28 7:08 ` [PATCH 01/13] btrfs-progs: move btrfs_extref_hash() to hash.h Lu Fengqi
2016-07-28 7:08 ` [PATCH 02/13] btrfs-progs: check: introduce function to find dir_item Lu Fengqi
2016-09-06 15:08 ` David Sterba
2016-07-28 7:08 ` [PATCH 03/13] btrfs-progs: check: introduce function to check inode_ref Lu Fengqi
2016-07-28 7:08 ` [PATCH 04/13] btrfs-progs: check: introduce function to check inode_extref Lu Fengqi
2016-07-28 7:08 ` [PATCH 05/13] btrfs-progs: check: introduce function to find inode_ref Lu Fengqi
2016-07-28 7:08 ` [PATCH 06/13] btrfs-progs: check: introduce a function to check dir_item Lu Fengqi
2016-07-28 7:08 ` [PATCH 07/13] btrfs-progs: check: introduce function to check file extent Lu Fengqi
2016-07-28 7:08 ` [PATCH 08/13] btrfs-progs: check: introduce function to check inode item Lu Fengqi
2016-07-28 7:08 ` [PATCH 09/13] btrfs-progs: check: introduce function to check fs root Lu Fengqi
2016-07-28 7:08 ` [PATCH 10/13] btrfs-progs: check: introduce function to check root ref Lu Fengqi
2016-07-28 7:08 ` [PATCH 11/13] btrfs-progs: check: introduce low_memory mode fs_tree check Lu Fengqi
2016-07-28 7:08 ` [PATCH 12/13] btrfs-progs: check: fix the return value bug of cmd_check() Lu Fengqi
2016-07-28 7:08 ` [PATCH 13/13] btrfs-progs: check: fix false warning for check_extent_item() Lu Fengqi
2016-08-17 17:00 ` [PATCH 00/13] btrfs-progs: check: check fs roots in low_memory mode David Sterba
2016-08-19 9:57 ` Wang Xiaoguang
2016-08-19 10:31 ` David Sterba [this message]
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=20160819103130.GF16983@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.com \
--cc=wangxg.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).