linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Kai Krakow <hurikhan77@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Mixing partitioned and non-partitioned discs in a RAID?
Date: Tue, 13 Sep 2016 09:55:50 -0600	[thread overview]
Message-ID: <CAJCQCtSCQ=deq3BrEcMecSOuiLERV=aqV9U74dF7zngyZOyKOg@mail.gmail.com> (raw)
In-Reply-To: <20160913002110.0c621dc2@jupiter.sol.kaishome.de>

On Mon, Sep 12, 2016 at 4:21 PM, Kai Krakow <hurikhan77@gmail.com> wrote:
> Am Sun, 21 Aug 2016 02:19:33 +0000 (UTC)
> schrieb Duncan <1i5t5.duncan@cox.net>:
>
>> Chris Murphy posted on Sat, 20 Aug 2016 18:36:21 -0600 as excerpted:
>>
>> > FAT leaves a lot to be desired but it's pretty universally
>> > supported and almost trivial to repair *if* the volume is
>> > repairable in the first place. The much bigger issue with ESP on
>> > Linux is this neurotic tendency of distros to persistently mount
>> > shit that does not need to be mounted. Like the ESP, and even the
>> > dedicated boot volume. They only need to be mounted when being
>> > updated and then should be umounted. And worse the convention is to
>> > do nested mount with /boot and then /boot/efi for the ESP so it's
>> > twice as bad a practice. By virtue of mounting the ESP the dirty
>> > bit is set, so any crash means it must be fsck'd and if that
>> > doesn't work, it's game over for that volume. Fragile setup.
>>
>> Depends on the distro.  On gentoo, you set it up the way you want of
>> course, but the recommendation has always been /boot, and now the
>> ESP, not mounted by default.
>>
>> But that would be /expected/ on gentoo, since being able to configure
>> it the way you want is the whole /point/ of running gentoo in the
>> first place.  Sort of like arch, only much more so.
>
> systemd systems (I'm booting Gentoo with systemd) should auto-mount ESP
> to /boot on access, and auto-unmount after a short timeout. So the
> solution to this problem is already wired into systemd if you use (a)
> proper GPT setup (with correct GUIDs) and (b) do not mention /boot in
> fstab.

What distro uses this layout by default? It's certainly incompatible
with multiboot where either Windows or macOS exist first. It also
necessitates an excessively large ESP to store all possible kernels
and initrds for every OS, making it all the harder to keep sync'd in
any case where even a simple raid1 setup is desired. The ESP is a file
system that doesn't support permissions, acls, or security labels
either. So I'm not really a fan of this, or even nested /boot/efi
either for that matter.  They should be mounted in /run only on demand
and only by the process that has permission to modify each.



-- 
Chris Murphy

      parent reply	other threads:[~2016-09-13 15:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20  4:00 Mixing partitioned and non-partitioned discs in a RAID? Bearcat Şándor
2016-08-20  6:02 ` Andrei Borzenkov
2016-08-20  6:52 ` Duncan
2016-08-20 15:21 ` Chris Murphy
2016-08-20 15:37   ` Chris Murphy
     [not found]   ` <BLU437-SMTP168169D258F02597287B2E92170@phx.gbl>
2016-08-21  0:36     ` Chris Murphy
2016-08-21  2:19       ` Duncan
2016-08-21  2:28         ` Bearcat Şándor
2016-09-12 22:21         ` Kai Krakow
2016-09-13  4:07           ` Duncan
2016-09-14 18:21             ` Kai Krakow
2016-09-13 15:55           ` Chris Murphy [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='CAJCQCtSCQ=deq3BrEcMecSOuiLERV=aqV9U74dF7zngyZOyKOg@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=hurikhan77@gmail.com \
    --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).