linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas D Steeves <nsteeves@gmail.com>
To: David Alcorn <nroclaed@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Install to or Recover RAID Array Subvolume Root?
Date: Mon, 25 Apr 2016 15:38:52 -0400	[thread overview]
Message-ID: <CAD=QJKjfrL1qbhDpE5W4vJZOyHKNd=G7+wCMapZSwUYs-dkOoQ@mail.gmail.com> (raw)
In-Reply-To: <CALq5X_iJcbXeaQxPAoHPwXyDSSXSx7HnWPApbQcXB4s7utGG_g@mail.gmail.com>

On 22 April 2016 at 06:44, David Alcorn <nroclaed@gmail.com> wrote:
>
> First, I verified that while the Debian Installer will install to a
> pre set default BTRFS RAID6 subvolume, the Grub install step fails.
> The alternative to restore installation to a RAID6 subvolume requires
> installation to a non RAID6 subvolume and then send|receive the
> snapshotted installation to the array.  To prepare for this attempt, I
> reinstalled BTRFS (Debian stable) to a flash drive using separate
> partitions for efi, /boot/ and / (in a subvolume).  The default
> subvolume was set to 5 for both the flash / partition and also the
> RAID6 array.  I used a separate /boot partition to reduce complexity.
> Both the kernel and btrfs tools were upgraded to 4.4.  I soon
> thereafter got lost.

1. Have you partially filled your RAID6 array?  If so, do you have
current backups for everything you care about?
2. Please indicate whether you prefer to mount by LABEL, UUID, or /dev
3. If it's by /dev, please send the output of: parted -l
4. If it's by LABEL or UUID, please also send the output of: blkid

Sincerely,
Nicholas

  reply	other threads:[~2016-04-25 19:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  5:22 Install to or Recover RAID Array Subvolume Root? David Alcorn
2016-04-18 12:31 ` Austin S. Hemmelgarn
2016-04-18 15:12   ` Chris Murphy
2016-04-18 15:15     ` Austin S. Hemmelgarn
2016-04-18 15:39       ` Chris Murphy
2016-04-18 15:52         ` Austin S. Hemmelgarn
2016-04-18 16:18           ` Chris Murphy
2016-04-18 20:34           ` Nicholas D Steeves
2016-04-19 11:14             ` Austin S. Hemmelgarn
2016-04-19 21:43               ` Nicholas D Steeves
2016-04-18 20:42 ` Nicholas D Steeves
2016-04-19  3:06   ` David Alcorn
2016-04-19 20:53     ` Nicholas D Steeves
2016-04-22 10:44   ` David Alcorn
2016-04-25 19:38     ` Nicholas D Steeves [this message]
2016-04-26  9:23       ` David Alcorn
2016-04-27 12:03         ` Nicholas D Steeves

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='CAD=QJKjfrL1qbhDpE5W4vJZOyHKNd=G7+wCMapZSwUYs-dkOoQ@mail.gmail.com' \
    --to=nsteeves@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nroclaed@gmail.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 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).