From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: degraded two-device btrfs raid1 (data/metadata) questions
Date: Sat, 1 Jun 2013 03:06:18 +0000 (UTC) [thread overview]
Message-ID: <pan$6834d$51a8a8e4$efe59dda$f34fd40d@cox.net> (raw)
In-Reply-To: pan$8e5ed$b63791f$8b3cc2f5$8c662141@cox.net
Duncan posted on Fri, 31 May 2013 14:24:25 +0000 as excerpted:
> Now, I'm setting up a minimal initramfs just to user-space mount the
> btrfs root properly so I don't have to mount it degraded.
>
> But I'm still left wondering how I'm supposed to tell whether it's
> actually running degraded or not, and how to sync everything back up if
> so.
FWIW, I'm up on the initramfs for the dual-device btrfs raid1 root, now.
It seems to work reasonably, altho I still have some fine tuning to do on
the initramfs (include gdisk/cgdisk, and I still want to see about
rolling my own instead of using dracut) once I have my other partitions
over on btrfs on the ssds.
Of course that means figuring out how to check for degraded raid1 btrfs
and how to "undegrade" it if necessary, is no longer simply theoretical,
altho I intend to be keep the reiserfs "spinning rust" backups current
for quite some time, given btrfs' development status.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2013-06-01 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 14:24 degraded two-device btrfs raid1 (data/metadata) questions Duncan
2013-06-01 3:06 ` Duncan [this message]
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='pan$6834d$51a8a8e4$efe59dda$f34fd40d@cox.net' \
--to=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).