From: Andrei Borzenkov <arvidjaar@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Debian Bullseye install btrfs raid1
Date: Wed, 4 May 2022 21:15:50 +0300 [thread overview]
Message-ID: <42d841fc-d4ee-37e1-470f-4ac5c821afc7@gmail.com> (raw)
In-Reply-To: <20220504121454.8a43384a5c8ec25d6e9c1b77@lucassen.org>
On 04.05.2022 13:14, richard lucassen wrote:
> On Wed, 4 May 2022 13:07:14 +0300
> Nikolay Borisov <nborisov@suse.com> wrote:
>
>>> The wiki explains how to repair an array, but when the array is the
>>> root fs you will have a problem.
>>>
>>> So, what should I do when the / fs is degraded?
>>
>> In case of btrfs raid1 if you managed to mount the array degraded
>> it's possible to add another device to the array and then run a
>> balance operation so that you end up with 2 copies of your data. I.e
>> I don't see a problem? Have I misunderstood you?
>
> I fear you did. I cannot mount it -o degraded, I have no working system!
>
> I need fysical access to the system to repair it, contrary to an md
> system, the latter will simply start as 'Degraded Array' even when I'm
> abroad...
>
No, it will not. Some script(s), as part of startup sequence, will
decide that array can be started even though it is degraded and force it
to be started. Nothing in principle prevents your distribution from
adding scripts to mount btrfs in degraded mode in this case. Those
scripts are not part of btrfs, so you should report it to your
distribution.
next prev parent reply other threads:[~2022-05-04 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 9:23 Debian Bullseye install btrfs raid1 richard lucassen
2022-05-04 9:27 ` Nikolay Borisov
2022-05-04 9:30 ` richard lucassen
2022-05-04 10:02 ` richard lucassen
2022-05-04 10:07 ` Nikolay Borisov
2022-05-04 10:14 ` richard lucassen
2022-05-04 10:26 ` Andy Smith
2022-05-04 11:16 ` richard lucassen
2022-05-04 18:15 ` Andrei Borzenkov [this message]
2022-05-04 19:33 ` richard lucassen
2022-05-05 8:27 ` Nikolay Borisov
2022-05-05 20:30 ` richard lucassen
2022-05-09 6:50 ` Andrei Borzenkov
2022-05-04 12:06 ` Hans van Kranenburg
2022-05-04 12:59 ` richard lucassen
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=42d841fc-d4ee-37e1-470f-4ac5c821afc7@gmail.com \
--to=arvidjaar@gmail.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 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.