linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: problem with degraded boot and systemd
Date: Tue, 20 May 2014 18:51:26 -0600	[thread overview]
Message-ID: <9289871B-275D-4994-8617-BD83EECCFB2B@colorremedies.com> (raw)
In-Reply-To: <pan$6f6ec$5ba926ea$9860d25c$5d86cd20@cox.net>


On May 20, 2014, at 6:03 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> 
> 
> I'd actually argue that's functioning as it should, since I see forced 
> manual intervention in ordered to mount degraded as a FEATURE, NOT A BUG.

Manual intervention is OK for now, when it takes the form of dropping to a dracut shell, and only requires the user to pass mount -o degraded. To mount degraded automatically is worse because within a notification API for user space, it will lead users to make bad choices resulting in data loss.

But the needed sequence is fairly burdensome: force shutdown, boot again, use rd.break=premount, then use mount -o degraded, and then exit a couple of times.


> [1] dracut: I use it here on gentoo as well, because my rootfs is a multi-
> device btrfs and a kernel rootflags=device= line won't parse correctly, 
> apparently due to splitting at the wrong =, so I must use an initr* 
> despite my preference for a direct initr*-less boot, and I use dracut to 
> generate it.

rootflags doesn't take a device argument, it only applies to the volume to be mounted at /sysroot, so only one = is needed.


Chris Murphy

  reply	other threads:[~2014-05-21  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19  0:54 problem with degraded boot and systemd Chris Murphy
2014-05-20 22:00 ` Goffredo Baroncelli
2014-05-20 22:26   ` Hugo Mills
2014-05-21  0:03     ` Duncan
2014-05-21  0:51       ` Chris Murphy [this message]
     [not found]       ` <4QrS1o00b1EMSLa01QrT4N>
2014-05-21 10:35         ` Duncan

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=9289871B-275D-4994-8617-BD83EECCFB2B@colorremedies.com \
    --to=lists@colorremedies.com \
    --cc=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).