All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Debian Bullseye install btrfs raid1
Date: Wed, 4 May 2022 13:07:14 +0300	[thread overview]
Message-ID: <9129a5be-f0a2-5859-4c02-eb075d222a31@suse.com> (raw)
In-Reply-To: <20220504120254.7fae6033bee9e63ed002bea9@lucassen.org>



On 4.05.22 г. 13:02 ч., richard lucassen wrote:
> On Wed, 4 May 2022 12:27:29 +0300
> Nikolay Borisov <nborisov@suse.com> wrote:
> 
>>> Question: is this newbie trying to set up an impossible config or
>>> have I missed something crucial somewhere?
>>
>> That's the default behavior, the reasoning is if you are missing one
>> device of a raid1 your data is at-risk in case the 2nd device fails.
>> You can override this behavior by mounting in degraded mode, that is
>> mount -odegraded
> 
> Another thing: sda3/sdb3 is the root fs, so I need to tell grub that
> it's ok to mount a degraded array (one or another way, don't know
> if it's possible, I'm not a grub guru). Adding it to fstab makes
> no sense as there is no fstab at that time.
> 
> OTOH, when using md devices, the / fs is mounted as Degraded Array and
> the remaining device remembers that this had happened. If the second
> disk is replaced I have to add it manually using mdadm. The first disk
> is "master". Using md the system boots and mounts / and thus all tools
> are available to repair the array.
> 
> 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?
> 
> R.
> 

  reply	other threads:[~2022-05-04 10:07 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 [this message]
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
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=9129a5be-f0a2-5859-4c02-eb075d222a31@suse.com \
    --to=nborisov@suse.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.