All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fleetwood <mike.fleetwood@googlemail.com>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: Don't error on resizing FS to same size
Date: Fri, 18 Nov 2011 08:14:29 +0000	[thread overview]
Message-ID: <20111118081428.GA27710@gmail.com> (raw)
In-Reply-To: <4EC5E470.4030605@csamuel.org>

On Fri, Nov 18, 2011 at 03:52:00PM +1100, Chris Samuel wrote:
> On 18/11/11 08:04, Mike Fleetwood wrote:
> 
> > It seems overly harsh to fail a resize of a btrfs file system to the
> > same size when a shrink or grow would succeed.  User app GParted trips
> > over this error.  Allow it by bypassing the shrink or grow operation.
> 
> OK - I'm a newbie with the code (and I'm looking at Linus's current git
> rather than any dev tree of Chris's), but...
> 
> > Signed-off-by: Mike Fleetwood <mike.fleetwood@googlemail.com>
> > ---
> [...]
> > ---
> >  fs/btrfs/ioctl.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> > index dae5dfe..00b7024 100644
> > --- a/fs/btrfs/ioctl.c
> > +++ b/fs/btrfs/ioctl.c
> > @@ -1251,7 +1251,7 @@ static noinline int btrfs_ioctl_resize(struct btrfs_root *root,
> >  		}
> >  		ret = btrfs_grow_device(trans, device, new_size);
> >  		btrfs_commit_transaction(trans, root);
> > -	} else {
> > +	} else if (new_size > old_size) {
> 
> shouldn't that be:
> 
> +	} else if (new_size < old_size) {
> 
> otherwise you'll never try and shrink if new_size is < old_size..
> 
> >  		ret = btrfs_shrink_device(device, new_size);
> >  	}
> >  

Chris, you're correct.  I have messed up a 1 line patch by rushing.
Will send corrected patch after some more testing!

Embarrassed,
Mike

      reply	other threads:[~2011-11-18  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 21:04 [PATCH] Btrfs: Don't error on resizing FS to same size Mike Fleetwood
2011-11-18  4:52 ` Chris Samuel
2011-11-18  8:14   ` Mike Fleetwood [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=20111118081428.GA27710@gmail.com \
    --to=mike.fleetwood@googlemail.com \
    --cc=chris@csamuel.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.