From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Su Yue <Damenly_Su@gmx.com>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/3] btrfs-progs: convert: report available space before convertion happens
Date: Wed, 29 Jul 2020 17:13:14 +0800 [thread overview]
Message-ID: <9904022e-8c16-bd93-960a-93f9019d19ba@gmx.com> (raw)
In-Reply-To: <8sf28zdt.fsf@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 4707 bytes --]
On 2020/7/29 下午5:05, Su Yue wrote:
>
> On Wed 29 Jul 2020 at 16:40, Qu Wenruo <wqu@suse.com> wrote:
>
>> Now if an ENOSPC error happened, the free space report would
>> help user to determine if it's a real ENOSPC or a bug in btrfs.
>>
>> The reported free space is the calculated free space, which
>> doesn't include super block space, nor merged data chunks.
>>
>> The free space is always smaller than the reported available
>> space of the original fs, as we need extra padding space for
>> used space to avoid too fragmented data chunks.
>>
>> The output exact would be:
>>
>> $ ./btrfs-convert /dev/nvme/btrfs create btrfs filesystem:
>> blocksize: 4096 nodesize: 16384 features: extref,
>> skinny-metadata (default) checksum: crc32c
>> free space report: free / total = 0 / 10737418240 (0%) <<<
>> ERROR: unable to create initial ctree: No space left on device
>> WARNING: an error occurred during conversion, the original
>> filesystem is not modified
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com> ---
>> convert/common.h | 9 +++++++++ convert/main.c | 26
>> ++++++++++++++++++++++++-- convert/source-fs.c | 1 + 3 files
>> changed, 34 insertions(+), 2 deletions(-)
>>
>> diff --git a/convert/common.h b/convert/common.h index
>> 7ec26cd996d3..2c7799433294 100644 --- a/convert/common.h +++
>> b/convert/common.h @@ -35,6 +35,7 @@ struct
>> btrfs_convert_context {
>> u64 inodes_count; u64 free_inodes_count; u64 total_bytes;
>> + u64 free_bytes_initial;
>> char *volume_name; const struct btrfs_convert_operations
>> *convert_ops;
>> @@ -47,6 +48,14 @@ struct btrfs_convert_context {
>> /* Free space which is not covered by data_chunks */ struct
>> cache_tree free_space;
>> + /* + * Free space reserved for ENOSPC report, it's just a
>> copy + * free_space. + * But after initial calculation,
>> free_space_initial is no longer + * updated, so we have a good
>> idea on how many free space we really + * have for btrfs. +
>> */ + struct cache_tree free_space_initial;
>> void *fs_data; };
>> diff --git a/convert/main.c b/convert/main.c index
>> 451e4f158689..49c95e092cbb 100644 --- a/convert/main.c +++
>> b/convert/main.c @@ -727,6 +727,23 @@ out:
>> return ret; }
>> +static int copy_free_space_tree(struct btrfs_convert_context
>> *cctx) +{ + struct cache_tree *src = &cctx->free_space; +
>> struct cache_tree *dst = &cctx->free_space_initial; + struct
>> cache_extent *cache; + int ret = 0; + + for (cache =
>> search_cache_extent(src, 0); cache; + cache =
>> next_cache_extent(cache)) { + ret =
>> add_merge_cache_extent(dst, cache->start, cache->size); + if
>> (ret < 0) + return ret; +
>> cctx->free_bytes_initial += cache->size; + } + return ret; +}
>> +
>> /*
>> * Read used space, and since we have the used space, *
>> calculate data_chunks and free for later mkfs
>> @@ -740,7 +757,10 @@ static int convert_read_used_space(struct
>> btrfs_convert_context *cctx)
>> return ret; ret = calculate_available_space(cctx);
>> - return ret; + if (ret < 0) + return ret; + + return
>> copy_free_space_tree(cctx);
>> } /*
>> @@ -1165,7 +1185,9 @@ static int do_convert(const char *devname,
>> u32 convert_flags, u32 nodesize,
>> printf("\tnodesize: %u\n", nodesize); printf("\tfeatures:
>> %s\n", features_buf); printf("\tchecksum: %s\n",
>> btrfs_super_csum_name(csum_type));
>> - + printf("free space report: free / total = %llu / %llu
>> (%lld%%)\n", + cctx.free_bytes_initial, cctx.total_bytes,
>> + cctx.free_bytes_initial * 100 / cctx.total_bytes);
>> memset(&mkfs_cfg, 0, sizeof(mkfs_cfg)); mkfs_cfg.csum_type =
>> csum_type; mkfs_cfg.label = cctx.volume_name;
>> diff --git a/convert/source-fs.c b/convert/source-fs.c index
>> f7fd3d6055b7..d2f7a825238d 100644 --- a/convert/source-fs.c +++
>> b/convert/source-fs.c @@ -74,6 +74,7 @@ void
>> init_convert_context(struct btrfs_convert_context *cctx)
>> cache_tree_init(&cctx->used_space);
>> cache_tree_init(&cctx->data_chunks);
>> cache_tree_init(&cctx->free_space);
>> + cache_tree_init(&cctx->free_space_initial);
>> } void clean_convert_context(struct btrfs_convert_context
>> *cctx)
>
> Did you forget the clean path? :)
Oh, thanks for that!
Just forgot that.
Thanks,
Qu
>
> ---
> Su
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-29 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 8:40 [PATCH 0/3] btrfs-progs: convert: better ENOSPC handling Qu Wenruo
2020-07-29 8:40 ` [PATCH 1/3] btrfs-progs: convert: handle errors better in ext2_copy_inodes() Qu Wenruo
2020-07-29 8:40 ` [PATCH 2/3] btrfs-progs: convert: update error message to reflect original fs unmodified cases Qu Wenruo
2020-07-29 8:40 ` [PATCH 3/3] btrfs-progs: convert: report available space before convertion happens Qu Wenruo
2020-07-29 9:05 ` Su Yue
2020-07-29 9:13 ` Qu Wenruo [this message]
2020-07-31 15:35 ` David Sterba
2020-07-31 16:16 ` [PATCH 0/3] btrfs-progs: convert: better ENOSPC handling David Sterba
2020-07-31 23:37 ` 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=9904022e-8c16-bd93-960a-93f9019d19ba@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=Damenly_Su@gmx.com \
--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).