From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: cannot boot with BTRFS in degraded mode
Date: Fri, 06 Sep 2019 10:00:49 +0900 [thread overview]
Message-ID: <87d0gexmpq.fsf@gmail.com> (raw)
In-Reply-To: <87a7bi25fv.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Thu, 05 Sep 2019 16:17:24 +0200")
Hello Giovanni!
Giovanni Biscuolo <g@xelera.eu> writes:
[...]
> [...] all I need to boot is entering the grub editing mode, boot
> degraded and solve the problem with "btrfs replace..." and "btrfs
> balance..."
>
> I was thinking to permanently add "rootflags=[...],degraded" as kernel
> parameter but reading the message I mentioned above:
>
> Altho if it is indeed true that btrfs will now refuse to mount writable
> if it's degraded like that, that's not such a huge issue either, as the
> read-only mount can serve as the same warning. Still, I certainly prefer
> the refusal to mount entirely without the degraded option, if indeed the
> filesystem is lacking a component device. There's nothing quite like
> forcing me to actually type in "rootflags=degraded" to rub my face in the
> reality and gravity of the situation I'm in! =:^)
>
> I changed my mind: booting in degraded mode should be done "manually"
> just to solve the issue :-)
Also note that for the time being, the init script of Guix doesn't honor
the "rootflags" kernel argument.
The good news is that there is a patch awaiting testing/review that adds
support for it here: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37305.
Cheers,
Maxim
next prev parent reply other threads:[~2019-09-06 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 14:36 cannot boot with BTRFS in degraded mode Giovanni Biscuolo
2019-09-04 20:49 ` Gábor Boskovits
2019-09-04 21:02 ` Gábor Boskovits
2019-09-05 14:17 ` Giovanni Biscuolo
2019-09-06 1:00 ` Maxim Cournoyer [this message]
2019-09-06 6:30 ` Giovanni Biscuolo
2019-09-06 7:20 ` Maxim Cournoyer
2019-09-06 9:47 ` Giovanni Biscuolo
2019-09-07 0:20 ` Maxim Cournoyer
2019-09-06 7:21 ` Christopher Baines
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=87d0gexmpq.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=g@xelera.eu \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.