From: Jim Salter <jim@jrs-s.net>
To: Freddie Cash <fjwcash@gmail.com>
Cc: "Joshua Schüler" <joshua.schueler@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
"Chris Murphy" <lists@colorremedies.com>
Subject: Re: btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT
Date: Fri, 03 Jan 2014 18:42:56 -0500 [thread overview]
Message-ID: <52C74B00.7080906@jrs-s.net> (raw)
In-Reply-To: <CAOjFWZ7zC3=4oH6=SBZA+PhZMrSK1KjxoRN6L2vqd=GTBKKTQA@mail.gmail.com>
For anybody else interested, if you want your system to automatically
boot a degraded btrfs array, here are my crib notes, verified working:
***************************** boot degraded
1. edit /etc/grub.d/10_linux, add degraded to the rootflags
GRUB_CMDLINE_LINUX="rootflags=degraded,subvol=${rootsubvol}
${GRUB_CMDLINE_LINUX}
2. add degraded to options in /etc/fstab also
UUID=bf9ea9b9-54a7-4efc-8003-6ac0b344c6b5 / btrfs
defaults,degraded,subvol=@ 0 1
3. Update and reinstall GRUB to all boot disks
update-grub
grub-install /dev/vda
grub-install /dev/vdb
Now you have a system which will automatically start a degraded array.
******************************************************
Side note: sorry, but I absolutely don't buy the argument that "the
system won't boot without you driving down to its physical location,
standing in front of it, and hammering panickily at a BusyBox prompt" is
the best way to find out your array is degraded. I'll set up a Nagios
module to check for degraded arrays using btrfs fi list instead, thanks...
On 01/03/2014 06:06 PM, Freddie Cash wrote:
> Why is manual intervention even needed? Why isn't the filesystem
> "smart" enough to mount in a degraded mode automatically?
>
> --
> Freddie Cash
> fjwcash@gmail.com <mailto:fjwcash@gmail.com>
next prev parent reply other threads:[~2014-01-03 23:40 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
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 [this message]
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=52C74B00.7080906@jrs-s.net \
--to=jim@jrs-s.net \
--cc=fjwcash@gmail.com \
--cc=joshua.schueler@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.