From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: <dsterba@suse.cz>
Subject: [PATCH v2 0/6] Lowmem mode check check fix for mulit-device
Date: Wed, 31 May 2017 13:56:04 +0800 [thread overview]
Message-ID: <20170531055610.11606-1-quwenruo@cn.fujitsu.com> (raw)
This patchset will fix a false alert in lowmem mode, which doesn't handle
RAID0/5/6/10 chunk well. (the 5th patch)
Along the lowmem fix, also enhance and cleanup some chunk verification code,
as lowmem mode and original mode are using different chunk verification.
(the 1st~4th patch)
Finally, cleanup the loop device setup and move it to test/common other
than handling in each test case. (the 6th patch)
changelog:
v2:
Fix a bug that single chunk is always treated as invalid, since its
profile is not power of 2.
Add the 6th patch to move the loop device setup to test/common.
Qu Wenruo (6):
btrfs-progs: Cleanup open-coded btrfs_chunk_item_size
btrfs-progs: Enhance chunk item validation check
btrfs-progs: check: Reuse btrfs_check_chunk_valid in lowmem mode
btrfs-progs: Introduce function to get correct stripe length
btrfs-progs: lowmem check: Fix false alert on missing chunk or dev
extent
btrfs-progs: test: Introduce functions to prepare and cleanup loop
device
cmds-check.c | 35 +++++------
tests/common | 38 ++++++++++++
.../misc-tests/006-image-on-missing-device/test.sh | 12 +---
tests/misc-tests/011-delete-missing-device/test.sh | 12 +---
tests/mkfs-tests/001-basic-profiles/test.sh | 12 +---
.../005-long-device-name-for-ssd/test.sh | 10 +---
tests/mkfs-tests/006-partitioned-loopdev/test.sh | 10 +---
volumes.c | 70 ++++++++++++++++++++--
volumes.h | 3 +
9 files changed, 136 insertions(+), 66 deletions(-)
--
2.13.0
next reply other threads:[~2017-05-31 5:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 5:56 Qu Wenruo [this message]
2017-05-31 5:56 ` [PATCH v2 1/6] btrfs-progs: Cleanup open-coded btrfs_chunk_item_size Qu Wenruo
2017-05-31 5:56 ` [PATCH v2 2/6] btrfs-progs: Enhance chunk item validation check Qu Wenruo
2017-05-31 5:56 ` [PATCH v2 3/6] btrfs-progs: check: Reuse btrfs_check_chunk_valid in lowmem mode Qu Wenruo
2017-05-31 5:56 ` [PATCH v2 4/6] btrfs-progs: Introduce function to get correct stripe length Qu Wenruo
2017-05-31 5:56 ` [PATCH v2 5/6] btrfs-progs: lowmem check: Fix false alert on missing chunk or dev extent Qu Wenruo
2017-05-31 5:56 ` [PATCH v2 6/6] btrfs-progs: test: Introduce functions to prepare and cleanup loop device Qu Wenruo
2017-06-02 14:05 ` David Sterba
2017-06-02 13:53 ` [PATCH v2 0/6] Lowmem mode check check fix for mulit-device 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=20170531055610.11606-1-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--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.