From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] btrfs-progs: image: Fix error when restoring multi-disk image to single disk
Date: Tue, 4 Dec 2018 11:34:20 +0100 [thread overview]
Message-ID: <20181204103419.GG17773@twin.jikos.cz> (raw)
In-Reply-To: <20181127083828.23861-1-wqu@suse.com>
On Tue, Nov 27, 2018 at 04:38:23PM +0800, Qu Wenruo wrote:
> This patchset can be fetched from github:
> https://github.com/adam900710/btrfs-progs/tree/image_recover
>
> The base commit is as usual, the latest stable tag, v4.19.
>
>
> Test case misc/021 will fail if using latest upstream kernel.
>
> This is due to the enhanced code in kernel to check block group <->
> chunk <-> dev extent mapping.
>
> This means from the very beginning, btrfs-image can't really restore a
> multi-disk image to single-disk one correctly.
>
> The problem is, although we modified chunk item, we didn't modify block
> group item's flags or dev extents.
>
> This patch will reset block group flags, then rebuild the whole
> dev extents by removing existing ones first, then re-add the correct
> dev extents calculated from chunk map.
>
> Now it could pass all misc tests and fsck tests.
>
> Changelog:
> v2:
> - Parameter list cleanup
> * Use trans->fs_info to remove fs_info parameter
> * Remove trans parameter for function who doesn't need
> - Merge dev extents removal code with rebuild code
> - Refactor btrfs_alloc_dev_extent() into 2 functions
> * btrfs_insert_dev_extent() for convert and dev extent rebuild
> * btrfs_alloc_dev_extent() for old use case
>
> Qu Wenruo (5):
> btrfs-progs: image: Refactor fixup_devices() to
> fixup_chunks_and_devices()
> btrfs-progs: image: Fix block group item flags when restoring
> multi-device image to single device
> btrfs-progs: volumes: Refactor btrfs_alloc_dev_extent() into two
> functions
> btrfs-progs: image: Remove all existing dev extents for later rebuild
> btrfs-progs: misc-tests/021: Do extra btrfs check before mounting
Merged to devel, thanks. I've switched strerror(-ret) to the errno
pattern.
prev parent reply other threads:[~2018-12-04 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 8:38 [PATCH v2 0/5] btrfs-progs: image: Fix error when restoring multi-disk image to single disk Qu Wenruo
2018-11-27 8:38 ` [PATCH v2 1/5] btrfs-progs: image: Refactor fixup_devices() to fixup_chunks_and_devices() Qu Wenruo
2018-11-27 8:46 ` Nikolay Borisov
2018-11-27 8:50 ` Qu Wenruo
2018-11-27 8:58 ` Nikolay Borisov
2018-12-04 10:18 ` David Sterba
2018-12-04 10:21 ` Qu Wenruo
2018-12-04 10:20 ` David Sterba
2018-12-04 10:22 ` Qu Wenruo
2018-11-27 8:38 ` [PATCH v2 2/5] btrfs-progs: image: Fix block group item flags when restoring multi-device image to single device Qu Wenruo
2018-11-27 8:38 ` [PATCH v2 3/5] btrfs-progs: volumes: Refactor btrfs_alloc_dev_extent() into two functions Qu Wenruo
2018-11-27 8:42 ` Nikolay Borisov
2018-11-27 8:38 ` [PATCH v2 4/5] btrfs-progs: image: Remove all existing dev extents for later rebuild Qu Wenruo
2018-11-27 8:38 ` [PATCH v2 5/5] btrfs-progs: misc-tests/021: Do extra btrfs check before mounting Qu Wenruo
2018-11-27 8:47 ` Nikolay Borisov
2018-12-04 10:34 ` 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=20181204103419.GG17773@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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).