From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 38435-done@debbugs.gnu.org
Subject: bug#38435: BTRFS open_ctree failed
Date: Mon, 01 Feb 2021 14:16:10 -0500 [thread overview]
Message-ID: <87v9bbr43p.fsf@gmail.com> (raw)
In-Reply-To: <87eexlagfv.fsf@yamatai> (Guillaume Le Vaillant's message of "Tue, 03 Dec 2019 10:47:48 +0100")
Hello,
Guillaume Le Vaillant <glv@posteo.net> writes:
[...]
>>> > (file-systems (cons* (file-system
>>> > (device (file-system-label "GUIX"))
>>> > (mount-point "/")
>>> > (options "lazytime,compress")
>>> > (type "btrfs"))
>>> > ;(file-system
>>> > ; (device (uuid "1234-ABCD" 'fat))
>>> > ; (mount-point "/boot/efi")
>>> > ; (type "vfat"))
>>> > %base-file-systems))
>>> >
>>>
>>> I just tried adding the 'lazytime' option to my root file system, and
>>> I got the same error as you when booting. Could you try removing it
>>> and see if it works?
>>>
>>> Until recently, the options declared in 'file-system' records were
>>> always ignored when mounting the root file system. Now they are taken
>>> into consideration, and I think it reveals a bug in the way file
>>> systems are mounted. If some options like 'lazytime' or 'defaults'
>>> are declared in a 'file-system' record (root file system or not),
>>> mounting it fails. However some other options like 'compress' or
>>> 'autodefrag' work fine.
>>>
>>> I suspect Guix adds some options by default when trying to mount file
>>> systems, and maybe we end up with conflicting options or doubled
>>> options that cause problems.
>>>
>>>
>>>
>>
>> I removed it and ran reconfigure and now it works.
>
> Applying patches #38462 and #38468 and changing the file system
> definition to the following should allow you to mount the root file
> system with the 'lazytime' option:
>
> (file-system
> (device (file-system-label "GUIX"))
> (mount-point "/")
> (flags '(lazy-time))
> (options "compress")
> (type "btrfs"))
I see these earlier patches of yours got merged already and the original
issue addressed.
Thank you!
Closing.
Maxim
next prev parent reply other threads:[~2021-02-01 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 13:45 bug#38435: BTRFS open_ctree failed raingloom
2019-11-30 14:53 ` Guillaume Le Vaillant
2019-11-30 16:01 ` Guillaume Le Vaillant
2019-12-01 11:02 ` raingloom
2019-12-03 9:47 ` Guillaume Le Vaillant
2021-02-01 19:16 ` Maxim Cournoyer [this message]
2020-02-18 16:29 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9bbr43p.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=38435-done@debbugs.gnu.org \
--cc=glv@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).