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:52:20 -0400 [thread overview]
Message-ID: <571502B4.2050401@gmail.com> (raw)
In-Reply-To: <CAJCQCtTSdnD+n9UR7hWtqLdBzjb6WQXF71XKTgKJNgZPcdA3fg@mail.gmail.com>
On 2016-04-18 11:39, Chris Murphy wrote:
> On Mon, Apr 18, 2016 at 9:15 AM, Austin S. Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>>
>>>
>> 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.
>
> No doubt this is a catch 22. I think it's reasonable for an installer
> to have an aging logic that allows it to be more conservative than the
> kernel's support for compat_ro_flags and incompat_flags, and refuse to
> install if it's not recently formatted.
>
> Now that I go look for this, I'm not sure what either flags offset
> 0x38 or compat_flags offset 0xac are about.
>
> Also, I didn't mention that Anaconda does require root fs to be in a
> new subvolume. It won't install to either subvolid 5, or any other
> existing subvolume.
>
I'm not certain about how Debian would handle it, but I think they'll
assume that the user knows what they're doing and just do what they say
(which can admittedly be a very dangerous assumption sometimes).
Like I said in one of my earlier e-mails though, these kind of
limitations are part of why I switched to Gentoo, there's no GUI
installer, but you can put the system together however the hell you want
(which is especially nice with BTRFS, because none of the installers out
there will let you use BTRFS on top of LVM, which is useful for things
like BTRFS raid1 on top of DM-RAID0).
next prev parent reply other threads:[~2016-04-18 15:52 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 [this message]
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=571502B4.2050401@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.