From: Chris Murphy <lists@colorremedies.com>
To: Alexandre Poux <pums974@gmail.com>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: multi-device btrfs with single data mode and disk failure
Date: Tue, 20 Sep 2016 14:02:05 -0600 [thread overview]
Message-ID: <CAJCQCtQUPxZHof4feS9Oxkm-tPUAc=gOib3Hf98W-j0ww59uwQ@mail.gmail.com> (raw)
In-Reply-To: <8b497ae5-7ed4-e22a-3f8c-fc3cb2d705df@gmail.com>
On Tue, Sep 20, 2016 at 1:54 PM, Alexandre Poux <pums974@gmail.com> wrote:
>
> OK, good idea, but to be able to do that, I have to use the patch that
> allow me to mount the partition in rw, otherwise I won't be able to
> shrink it I suppose..
> And even with the patch I'm not sure that I won't get an IO error the
> same way I get it when I try to remove the device.
> I will try it on my virtual machine.
The shrink itself is pretty trivial in that its just moving block
groups around if necessary, it's part of the balance code, there's not
much metadata being changed, just CoW the block groups, and then
update the chunk tree and supers. It is trickier when it comes to
either partition map changes while the fs is still mounted; or doing
it the way I was describing by deleting one of the present devices in
which case you can then just use that now empty partition as a starter
for a new file system.
It's a catch 22 either way.
Note that by default if you don't specify a devid for shrink, it's
only resizing devid1.
--
Chris Murphy
next prev parent reply other threads:[~2016-09-20 20:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 7:44 multi-device btrfs with single data mode and disk failure Alexandre Poux
2016-09-15 15:38 ` Chris Murphy
2016-09-15 16:30 ` Alexandre Poux
2016-09-15 16:54 ` Chris Murphy
[not found] ` <760be1b7-79b2-a25d-7c60-04ceac1b6e40@gmail.com>
2016-09-15 21:54 ` Chris Murphy
2016-09-19 22:05 ` Alexandre Poux
2016-09-20 17:03 ` Alexandre Poux
2016-09-20 17:54 ` Chris Murphy
2016-09-20 18:19 ` Alexandre Poux
2016-09-20 18:38 ` Chris Murphy
2016-09-20 18:53 ` Alexandre Poux
2016-09-20 19:11 ` Chris Murphy
[not found] ` <4e7ec5eb-7fb6-2d19-f29d-82461e2d0bd2@gmail.com>
2016-09-20 19:46 ` Chris Murphy
2016-09-20 20:18 ` Alexandre Poux
2016-09-20 21:05 ` Alexandre Poux
2016-09-20 21:15 ` Chris Murphy
2016-09-29 12:55 ` Alexandre Poux
2016-09-30 23:46 ` Alexandre Poux
2016-09-20 19:43 ` Austin S. Hemmelgarn
2016-09-20 19:54 ` Alexandre Poux
2016-09-20 20:02 ` Chris Murphy [this message]
2016-09-20 19:55 ` Chris Murphy
2016-09-21 11:07 ` Austin S. Hemmelgarn
2016-09-20 20:59 ` Graham Cobb
2016-09-20 18:56 ` Austin S. Hemmelgarn
2016-09-20 19:06 ` Alexandre Poux
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='CAJCQCtQUPxZHof4feS9Oxkm-tPUAc=gOib3Hf98W-j0ww59uwQ@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pums974@gmail.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).