All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: David Alcorn <nroclaed@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Install to or Recover RAID Array Subvolume Root?
Date: Mon, 18 Apr 2016 11:15:59 -0400	[thread overview]
Message-ID: <5714FA2F.6010207@gmail.com> (raw)
In-Reply-To: <CAJCQCtRQ_1-peN6QVd53P63xQUqxfvmth4aEbwXrpaCyjVds=Q@mail.gmail.com>

On 2016-04-18 11:12, Chris Murphy wrote:
> On Mon, Apr 18, 2016 at 6:31 AM, Austin S. Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>> On 2016-04-18 01:22, David Alcorn wrote:
>>>
>>>
>>> I erred and shutdown my NAS during a balance.  Grub lost track of my
>>> root.  Root was on RAID 6 array subvolid 257.  I can boot a different
>>> root from a USB flash drive but neither update-grub not install-grub
>>> sees my old root on array subvolid 257.  I am happy to either recover
>>> or lose array subvolid 257 but do not want to lose data on other array
>>> subvol's.  I prefer to have my root on the array rather than a flash
>>> drive.  The balance completed successfully after I booted from the
>>> flash drive.
>>>
>>> I am running a debian back-ported 4.4.0 kernel with btrfs-progs v4.4
>>> on both my flash drive and array subvolid 257.  Both installs are
>>> UEFI.
>>
>> It's rather refreshing to see somebody using an up to date kernel and
>> userspace for once.  The issue with GRUB is however likely an issue with
>> GRUB itself though (or possibly with something it uses for detecting
>> filesystems), which brings up the question: How recent is the version of
>> GRUB you're trying to install?  I would not be surprised if their current
>> support for BTRFS raid5 and raid6 is not particularly good, especially
>> considering that their support for BTRFS raid1 was kind of shoddy at first
>> (and it still has occasional issues, like not working right half the time if
>> one of the devices is missing).
>
> I can't tell if this setup is Btrfs on md/mdadm raid6, or if it's
> Btrfs raid6? GRUB has supported mdadm raid6 for a long time, but I
> don't think it understands Btrfs raid56 at all.
>
> The only GUI installer I know that explicitly permits installation of
> an OS to an existing Btrfs is Anaconda (mainly Red Hat and Fedora).
> There's a bug in the storage backend that prevents this from working
> in Fedora 23, exposed by a Btrfs change disallowing simultaneous use
> of subvolid and subvol, resulting in mount failure, which in turn
> causes the installer to crash. But it works in Fedora 22, and it will
> work in Fedora 24. On the other hand, no Fedora supports Btrfs for
> /boot, it has to be separate and it has to be ext4 or XFS (and maybe
> FAT).
>
I don't know about the current state of the Debian installer, but I know 
back when I used Debian regularly and used the standard text based 
installer, as long as I didn't format things from the UI, I could 
provision the filesystems however the hell I wanted manually and point 
the installer at the appropriate ones for each mount point, and it worked.

  reply	other threads:[~2016-04-18 15:17 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 [this message]
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
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=5714FA2F.6010207@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --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 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.