From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Why is converting from RAID1 to single in Btrfs an I/O-intensive operation?
Date: Sat, 18 Feb 2023 12:38:16 +0100 [thread overview]
Message-ID: <87a61bi4pj.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: 04ddea4e-4823-00dc-c32c-700d9f7e1fef@libero.it
Hallöchen!
Goffredo Baroncelli writes:
> On 18/02/2023 09.10, Torsten Bronger wrote:
>
>
>> I want to replace a device in a RAID1 and converted it
>> temporarily to “single”:
>
> I suggest you to evaluate
> - remove a disk when the FS is offline
> - mount the FS in 'degraded' mode
> - attach a new disk
I agree that converting to single is not the fastest way to replace
a disk, but the safest AFAICS. It is the boot partition in a simple
home server without monitor or keyboard, which makes mounting as
degraded difficult. Besides, you can only mount in degraded mode
once. If anything goes wrong, I have to rebuild from scratch.
Mileage may vary in a more professional environment.
Regards,
Torsten.
--
Torsten Bronger
next prev parent reply other threads:[~2023-02-18 11:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 8:10 Why is converting from RAID1 to single in Btrfs an I/O-intensive operation? Torsten Bronger
2023-02-18 8:54 ` Andrei Borzenkov
2023-02-18 11:32 ` Torsten Bronger
2023-02-18 10:46 ` Goffredo Baroncelli
2023-02-18 11:38 ` Torsten Bronger [this message]
2023-02-18 17:47 ` me
2023-02-18 20:05 ` Torsten Bronger
2023-02-18 21:46 ` me
2023-02-19 10:09 ` Goffredo Baroncelli
2023-02-19 19:04 ` Torsten Bronger
2023-02-19 23:39 ` waxhead
2023-02-20 6:31 ` Torsten Bronger
2023-02-20 9:38 ` Patrik Lundquist
2023-02-20 15:48 ` Forza
2023-02-21 7:18 ` Torsten Bronger
2023-02-21 11:35 ` me
2023-02-22 8:30 ` Torsten Bronger
2023-02-26 18:52 ` Ferry Toth
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=87a61bi4pj.fsf@physik.rwth-aachen.de \
--to=bronger@physik.rwth-aachen.de \
--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