linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Hans van Kranenburg <hans@knorrie.org>, Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/6] btrfs-progs: Support for BG_TREE feature
Date: Tue, 26 Feb 2019 09:29:33 +0800	[thread overview]
Message-ID: <c268ed19-f472-be89-b8e5-68d1b055eecd@gmx.com> (raw)
In-Reply-To: <8a88277e-6a9f-7383-601f-cb6e84451ce5@knorrie.org>


[-- Attachment #1.1: Type: text/plain, Size: 3193 bytes --]



On 2019/2/26 上午12:36, Hans van Kranenburg wrote:
> Sorry to bother you again...
> 
> On 12/28/18 9:38 AM, Qu Wenruo wrote:
>> This patchset can be fetched from github:
>> https://github.com/adam900710/btrfs-progs/tree/bg_tree
>> The basis commit is:
>>
>> commit 7d16a2b460182ee98c649533a6975b6e419c3d71
>> Author: Qu Wenruo <wqu@suse.com>
>> Date:   Thu Dec 27 13:49:18 2018 +0800
>>
>>     btrfs-progs: Create uuid tree with proper contents
>>
>> Which is further based on devel branch.
>>
>> This patchset provides the needed user space infrastructure for BG_TREE
>> feature.
>>
>> Since it's an new exclusive feature, unlike SKINNY_METADATA, btrfs-progs
>> is needed to convert existing fs (unmounted) to new format.
>>
>> Although I have prepared the functionality, convert_to_bg_tree(), and
>> already uses it in mkfs, I haven't decided if I should put it under
>> btrfstune, as btrfstune isn't such offline convert tool.
> 
> Ok, so, the convert_to_bg_tree still needs wiring up somewhere before
> it's possible to convert an existing fs?

Sorry, I haven't investigate more time for this convert.
It's more or less expected to be something use it or not so far.

> 
> I want to test with a (iSCSI level clone of a) rather large-ish
> filesystem, so I was searching for how to convert that in place.
> 
> Do you have an idea for a (quick hack?) way to make this happen?

Btrfs-progs needs extra patch for it, but I haven't implemented it yet.
It shouldn't be super complex, but I'm not confident enough yet.

If nothing goes wrong, I'll update the btrfs-progs patchset this week
with (maybe PoC) offline convert.

Thanks,
Qu
> 
> Doing the offline conversion itself is also already an interesting
> thing, seeing how it behaves with some tens of thousands of block
> groups... (As the intended audience for it will mostly be people having
> large filesystems already.)
> 
>> If anyone has better idea on the new convert tool interface, I'm all
>> ears.
>>
>> For the performance improvement, please check the kernel patchset cover
>> letter or the last patch.
>> (SPOILER ALERT: It's super fast)
>>
>> Qu Wenruo (6):
>>   btrfs-progs: Refactor excluded extent functions to use fs_info
>>   btrfs-progs: Refactor btrfs_read_block_groups()
>>   btrfs-progs: Enable read-write ability for 'bg_tree' feature
>>   btrfs-progs: mkfs: Introduce -O bg-tree
>>   btrfs-progs: dump-tree/dump-super: Introduce support for bg tree
>>   btrfs-progs: check: Introduce support for bg-tree feature
>>
>>  check/main.c              |   7 +-
>>  check/mode-lowmem.c       |   9 +-
>>  cmds-inspect-dump-super.c |   3 +-
>>  cmds-inspect-dump-tree.c  |   5 +
>>  ctree.h                   |  17 +-
>>  disk-io.c                 |  29 +++-
>>  extent-tree.c             | 326 +++++++++++++++++++++++++++-----------
>>  fsfeatures.c              |   6 +
>>  mkfs/common.c             |   7 +-
>>  mkfs/common.h             |   1 +
>>  mkfs/main.c               |  57 +++++++
>>  print-tree.c              |   3 +
>>  transaction.c             |   1 +
>>  13 files changed, 365 insertions(+), 106 deletions(-)
>>
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2019-02-26  1:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-28  8:38 [PATCH 0/6] btrfs-progs: Support for BG_TREE feature Qu Wenruo
2018-12-28  8:38 ` [PATCH 1/6] btrfs-progs: Refactor excluded extent functions to use fs_info Qu Wenruo
2018-12-28  8:38 ` [PATCH 2/6] btrfs-progs: Refactor btrfs_read_block_groups() Qu Wenruo
2018-12-28  8:38 ` [PATCH 3/6] btrfs-progs: Enable read-write ability for 'bg_tree' feature Qu Wenruo
2018-12-28  8:38 ` [PATCH 4/6] btrfs-progs: mkfs: Introduce -O bg-tree Qu Wenruo
2018-12-28  8:38 ` [PATCH 5/6] btrfs-progs: dump-tree/dump-super: Introduce support for bg tree Qu Wenruo
2018-12-28  8:38 ` [PATCH 6/6] btrfs-progs: check: Introduce support for bg-tree feature Qu Wenruo
2019-02-25 16:36 ` [PATCH 0/6] btrfs-progs: Support for BG_TREE feature Hans van Kranenburg
2019-02-26  1:29   ` Qu Wenruo [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=c268ed19-f472-be89-b8e5-68d1b055eecd@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=hans@knorrie.org \
    --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).