public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle Ambroff-Kao <kyle@ambroffkao.com>
To: linux-btrfs@vger.kernel.org
Cc: Kyle Ambroff-Kao <kyle@ambroffkao.com>
Subject: [PATCH 0/1] Support replacing a device with smaller one
Date: Sun,  8 Dec 2019 01:30:44 -0800	[thread overview]
Message-ID: <20191208093045.43433-1-kyle@ambroffkao.com> (raw)

This is a pretty simple patch to address Bug 112741: "btrfs device
replace" should allow smaller devices if possible[1].

I have a followup patch for btrfs-progs related to this which updates
the validation and adds an extra prompt.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=112741

Kyle Ambroff-Kao (1):
  btrfs: Allow replacing device with a smaller one if possible

 fs/btrfs/dev-replace.c | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-12-08  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08  9:30 Kyle Ambroff-Kao [this message]
2019-12-08  9:30 ` [PATCH 1/1] btrfs: Allow replacing device with a smaller one if possible Kyle Ambroff-Kao
2019-12-09 10:26   ` Filipe Manana
2019-12-09 19:22     ` Kyle Ambroff-Kao
2019-12-13 15:48     ` 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=20191208093045.43433-1-kyle@ambroffkao.com \
    --to=kyle@ambroffkao.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox