From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, yoasif@gmail.com, rrauenza@gmail.com
Subject: [PATCH 0/4] btrfs-progs repair support for unaligned/mismatched device sizes
Date: Tue, 10 Oct 2017 07:51:09 +0000 [thread overview]
Message-ID: <20171010075113.10718-1-quwenruo.btrfs@gmx.com> (raw)
The patchset can be fetched from github:
https://github.com/adam900710/btrfs-progs/tree/check_unaligned_dev
There are several reports in mail list for btrfs device size related
problems.
1) Unmountable fs, due to mismatched super total_bytes
Unmountable if super total_bytes is smaller than total rw bytes of
all devices.
Root cause under investigation, but only one report here.
This patchset provides the tool to fix it offline.
(At least better than unmountable forever)
2) Harmless kernel warning for btrfs_update_device()
v4.14 introduced restrict device size checker.
This somewhat break the backward compatibility and causing kernel
warning.
It can be fixed online with "btrfs filesystem resize".
(Although it is better to fixed it at mount time)
This patchset also provide a fallback method to fix it.
Qu Wenruo (4):
btrfs-progs: Introduce functions to repair unaligned/mismatch device
size
btrfs-progs: fsck: Introduce --fix-dev-size option
btrfs-progs: check: Also check unalignment/mismatch device and super
size
btrfs-progs: test/fsck: Add test case image for --fix-dev-size
Qu Wenruo (4):
btrfs-progs: Introduce functions to repair unaligned/mismatch device
size
btrfs-progs: fsck: Introduce --fix-dev-size option
btrfs-progs: check: Also check unalignment/mismatch device and super
size
btrfs-progs: test/fsck: Add test case image for --fix-dev-size
Documentation/btrfs-check.asciidoc | 23 ++
cmds-check.c | 292 ++++++++++++++++++++-
.../dev_and_super_mismatch_unaligned.raw.xz | Bin 0 -> 21536 bytes
3 files changed, 314 insertions(+), 1 deletion(-)
create mode 100644 tests/fsck-tests/027-unaligned-super-dev-sizes/dev_and_super_mismatch_unaligned.raw.xz
--
2.14.2
next reply other threads:[~2017-10-10 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 7:51 Qu Wenruo [this message]
2017-10-10 7:51 ` [PATCH 1/4] btrfs-progs: Introduce functions to repair unaligned/mismatch device size Qu Wenruo
2017-10-10 8:24 ` Nikolay Borisov
2017-10-10 7:51 ` [PATCH 2/4] btrfs-progs: fsck: Introduce --fix-dev-size option Qu Wenruo
2017-10-10 13:16 ` David Sterba
2017-10-11 0:43 ` Qu Wenruo
2017-10-26 18:58 ` David Sterba
2017-10-27 0:50 ` Qu Wenruo
2017-10-10 7:51 ` [PATCH 3/4] btrfs-progs: check: Also check unalignment/mismatch device and super size Qu Wenruo
2017-10-10 8:31 ` Nikolay Borisov
2017-10-10 8:34 ` Qu Wenruo
2017-10-10 7:51 ` [PATCH 4/4] btrfs-progs: test/fsck: Add test case image for --fix-dev-size Qu Wenruo
2017-10-10 8:15 ` [PATCH 0/4] btrfs-progs repair support for unaligned/mismatched device sizes Nikolay Borisov
2017-10-10 8:31 ` Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2017-10-17 6:06 Ursul Hempel Egal
2017-10-17 8:15 ` 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=20171010075113.10718-1-quwenruo.btrfs@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=rrauenza@gmail.com \
--cc=yoasif@gmail.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).