All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Salter <jim@jrs-s.net>
To: "Hugo Mills" <hugo@carfax.org.uk>,
	"Joshua Schüler" <joshua.schueler@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT
Date: Fri, 03 Jan 2014 18:25:30 -0500	[thread overview]
Message-ID: <52C746EA.7000006@jrs-s.net> (raw)
In-Reply-To: <20140103231821.GJ8913@carfax.org.uk>

Yep - had just figured that out and successfully booted with it, and was 
in the process of typing up instructions for the list (and posterity).

One thing that concerns me is that edits made directly to grub.cfg will 
get wiped out with every kernel upgrade when update-grub is run - any 
idea where I'd put this in /etc/grub.d to have a persistent change?

I have to tell you, I'm not real thrilled with this behavior either way 
- it means I can't have the option to automatically mount degraded 
filesystems without the filesystems in question ALWAYS showing as being 
mounted degraded, whether the disks are all present and working fine or 
not. That's kind of blecchy. =\


On 01/03/2014 06:18 PM, Hugo Mills wrote:
> On Fri, Jan 03, 2014 at 06:13:25PM -0500, Jim Salter wrote:
>> Sorry - where do I put this in GRUB? /boot/grub/grub.cfg is still
>> kinda black magic to me, and I don't think I'm supposed to be
>> editing it directly at all anymore anyway, if I remember
>> correctly...
>     You don't need to edit grub.cfg -- when you boot, grub has an edit
> option, so you can do it at boot time without having to use a rescue
> disk.
>
>     Regardless, the thing you need to edit is the line starting
> "linux", and will look something like this:
>
> linux /vmlinuz-3.11.0-rc2-dirty root=UUID=1b6ec419-211a-445e-b762-ae7da27b6e8a ro single rootflags=subvol=fs-root
>
>     If there's a rootflags= option already (as above), add ",degraded"
> to the end. If there isn't, add "rootflags=degraded".
>
>     Hugo.
>
>>>> HOWEVER - this won't allow a root filesystem to mount. How do you deal
>>>> with this if you'd set up a btrfs-raid1 or btrfs-raid10 as your root
>>>> filesystem? Few things are scarier than seeing the "cannot find init"
>>>> message in GRUB and being faced with a BusyBox prompt... which is
>>>> actually how I initially got my scare; I was trying to do a walkthrough
>>>> for setting up a raid1 / for an article in a major online magazine and
>>>> it wouldn't boot at all after removing a device; I backed off and tested
>>>> with a non root filesystem before hitting the list.
>>> Add -o degraded to the boot-options in GRUB.


  reply	other threads:[~2014-01-03 23:23 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 22:28 btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT Jim Salter
2014-01-03 22:42 ` Emil Karlson
2014-01-03 22:43 ` Joshua Schüler
2014-01-03 22:56   ` Jim Salter
2014-01-03 23:04     ` Hugo Mills
2014-01-03 23:04     ` Joshua Schüler
2014-01-03 23:13       ` Jim Salter
2014-01-03 23:18         ` Hugo Mills
2014-01-03 23:25           ` Jim Salter [this message]
2014-01-03 23:32             ` Chris Murphy
2014-01-03 23:22         ` Chris Murphy
2014-01-04  6:10           ` Duncan
2014-01-04 11:20             ` Chris Samuel
2014-01-04 13:03               ` Duncan
2014-01-04 14:51             ` Chris Mason
2014-01-04 15:23               ` Goffredo Baroncelli
2014-01-04 20:08               ` Duncan
2014-01-04 21:22             ` Jim Salter
2014-01-05 11:01               ` Duncan
2014-01-03 23:19     ` Chris Murphy
     [not found]     ` <CAOjFWZ7zC3=4oH6=SBZA+PhZMrSK1KjxoRN6L2vqd=GTBKKTQA@mail.gmail.com>
2014-01-03 23:42       ` Jim Salter
2014-01-03 23:45         ` Jim Salter
2014-01-04  0:27         ` Chris Murphy
2014-01-04  2:59           ` Jim Salter
2014-01-04  5:57             ` Dave
2014-01-04 11:28               ` Chris Samuel
2014-01-04 14:56                 ` Chris Mason
2014-01-05  9:20                   ` Chris Samuel
2014-01-05 11:16                     ` Duncan
2014-01-04 19:18             ` Chris Murphy
2014-01-04 21:16               ` Jim Salter
2014-01-05 20:25                 ` Chris Murphy
2014-01-06 10:20                   ` Chris Samuel
2014-01-06 18:30                     ` Chris Murphy
2014-01-06 19:25                       ` Jim Salter
2014-01-06 22:05                         ` Chris Murphy
2014-01-06 22:24                           ` Jim Salter
2014-01-07  5:43                         ` Chris Samuel
2014-01-06 19:31                       ` correct way to rollback a root filesystem? Jim Salter
2014-01-07 11:55                         ` Sander

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=52C746EA.7000006@jrs-s.net \
    --to=jim@jrs-s.net \
    --cc=hugo@carfax.org.uk \
    --cc=joshua.schueler@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.