From: Su Yue <suy.fnst@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH 3/5] btrfs-progs: check: enable lowmem repair
Date: Tue, 11 Apr 2017 11:26:29 +0800 [thread overview]
Message-ID: <20170411032631.24932-4-suy.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <20170411032631.24932-1-suy.fnst@cn.fujitsu.com>
Enable btrfsck option '--repair' with option '--mode=lowmem'.
Now lowmem mode only repairs wrong nbytes, dir isize.
Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
---
cmds-check.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/cmds-check.c b/cmds-check.c
index 6ab18b26..da5fe75f 100644
--- a/cmds-check.c
+++ b/cmds-check.c
@@ -12925,11 +12925,10 @@ int cmd_check(int argc, char **argv)
}
/*
- * Not supported yet
+ * Support partially
*/
if (repair && check_mode == CHECK_MODE_LOWMEM) {
- error("low memory mode doesn't support repair yet");
- exit(1);
+ warning("low memory mode support repair partially");
}
radix_tree_init();
--
2.12.0
next prev parent reply other threads:[~2017-04-11 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 3:26 [PATCH 0/5] btrfs-progs: check: simple errors repair in lowmem Su Yue
2017-04-11 3:26 ` [PATCH 1/5] btrfs-progs: check: inode nbytes fix " Su Yue
2017-04-11 3:26 ` [PATCH 2/5] btrfs-progs: check: dir isize " Su Yue
2017-04-11 3:26 ` Su Yue [this message]
2017-04-11 3:26 ` [PATCH 4/5] btrfs-progs: fsck-check: Allow fsck check test to repair in lowmem mode for certain test cases Su Yue
2017-04-11 3:26 ` [PATCH 5/5] btrfs-progs: fsck-check: test cases for nbytes and dir isize Su Yue
2017-05-17 8:25 ` [PATCH 0/5] btrfs-progs: check: simple errors repair in lowmem Su Yue
2017-06-01 14:47 ` David Sterba
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=20170411032631.24932-4-suy.fnst@cn.fujitsu.com \
--to=suy.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
/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.