From: Boris Burkov <boris@bur.io>
To: 20210419124541.148269-1-l@damenly.su
Cc: linux-btrfs@vger.kernel.org, l@damenly.su,
Chris Murphy <lists@colorremedies.com>
Subject: Re: [PATCH v3] btrfs-progs: fi resize: fix false 0.00B sized output
Date: Mon, 3 May 2021 10:19:55 -0700 [thread overview]
Message-ID: <YJAwrUMlRK6dWXJv@zen> (raw)
In-Reply-To: <20210420045827.150881-1-l@damenly.su>
On Tue, Apr 20, 2021 at 12:58:27PM +0800, Su Yue wrote:
> Resize to nums without sign prefix makes false output:
> btrfs fi resize 1:150g /srv/extra
> Resize device id 1 (/dev/sdb1) from 298.09GiB to 0.00B
>
> The resize operation would take effect though.
>
> check_resize_args() does not handle the mod 0 case and new_size is 0.
> Simply assigning @diff to @new_size to fix this.
>
> Issue: #307
> Reported-by: Chris Murphy <lists@colorremedies.com>
> Signed-off-by: Su Yue <l@damenly.su>
Reviewed-by: Boris Burkov <boris@bur.io>
> ---
> Changelog:
> v3:
> Just assign @diff to @new_size. (Boris Burkov)
> v2:
> Calculate u64 diff using max() and min().
> Calculate mod by comparing new and old size.
> ---
> cmds/filesystem.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/cmds/filesystem.c b/cmds/filesystem.c
> index 9e3cce687d6e..b4c09768235c 100644
> --- a/cmds/filesystem.c
> +++ b/cmds/filesystem.c
> @@ -1158,7 +1158,10 @@ static int check_resize_args(const char *amount, const char *path) {
> }
> old_size = di_args[dev_idx].total_bytes;
>
> - if (mod < 0) {
> + /* For target sizes without '+'/'-' sign prefix(e.g. 1:150g) */
> + if (mod == 0) {
> + new_size = diff;
> + } else if (mod < 0) {
> if (diff > old_size) {
> error("current size is %s which is smaller than %s",
> pretty_size_mode(old_size, UNITS_DEFAULT),
> --
> 2.30.1
>
next prev parent reply other threads:[~2021-05-03 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 4:58 [PATCH v3] btrfs-progs: fi resize: fix false 0.00B sized output Su Yue
2021-05-03 17:19 ` Boris Burkov [this message]
2021-05-06 14:21 ` 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=YJAwrUMlRK6dWXJv@zen \
--to=boris@bur.io \
--cc=20210419124541.148269-1-l@damenly.su \
--cc=l@damenly.su \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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