From: Su Yue <suy.fnst@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH 0/5] btrfs-progs: check: simple errors repair in lowmem
Date: Tue, 11 Apr 2017 11:26:26 +0800 [thread overview]
Message-ID: <20170411032631.24932-1-suy.fnst@cn.fujitsu.com> (raw)
The series include following contents:
1) Repair wrong nbytes of file inode item.
After traversal of extents in one file, we should get the actual nbytes
of the file. If nbytes in the file inode differs from the actual value,
set the value to actual one.
The wrong nbytes of file inode case corresponds to fsck-test/016.
2) Repair wrong iszie of directory inode item.
After traversal of dir_index and dir_item in one dir, we should get
the actual isize of the dirctory. If size in the inode item differs
from the actual value, set the value to actual one.
New test case 'fsck-test/026' is added for the case wrong isize of
directory inode.
3) Allow fsck check test to repair in lowmem mode for certain test cases
if TEST_ENABLE_OVERRIDE=true.
Qu Wenruo (1):
btrfs-progs: fsck-check: Allow fsck check test to repair in lowmem
mode for certain test cases
Su Yue (4):
btrfs-progs: check: inode nbytes fix in lowmem
btrfs-progs: check: dir isize fix in lowmem
btrfs-progs: check: enable lowmem repair
btrfs-progs: fsck-check: test cases for nbytes and dir isize
cmds-check.c | 149 +++++++++++++++++++--
tests/common.local | 14 +-
.../016-wrong-inode-nbytes/.lowmem_repairable | 0
.../026-wrong-dir-inode-isize/.lowmem_repairable | 0
.../026-wrong-dir-inode-isize/default_case.img | Bin 0 -> 4096 bytes
5 files changed, 153 insertions(+), 10 deletions(-)
create mode 100644 tests/fsck-tests/016-wrong-inode-nbytes/.lowmem_repairable
create mode 100644 tests/fsck-tests/026-wrong-dir-inode-isize/.lowmem_repairable
create mode 100644 tests/fsck-tests/026-wrong-dir-inode-isize/default_case.img
--
2.12.0
next 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 Su Yue [this message]
2017-04-11 3:26 ` [PATCH 1/5] btrfs-progs: check: inode nbytes fix in lowmem Su Yue
2017-04-11 3:26 ` [PATCH 2/5] btrfs-progs: check: dir isize " Su Yue
2017-04-11 3:26 ` [PATCH 3/5] btrfs-progs: check: enable lowmem repair Su Yue
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-1-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.