From: Alex Kost <alezost@gmail.com>
To: 25573@debbugs.gnu.org
Subject: bug#25573: Adding btrfs support may break reconfigured system
Date: Sun, 29 Jan 2017 21:03:56 +0300 [thread overview]
Message-ID: <87wpddzqsz.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
Hello, recently I found that "guix system" makes a "broken" system for
me. When I boot a freshly created system, I get something like this:
In procedure <...> at ./gnu/build/file-systems.scm:282:4 (device)
In procedure fport_seek: Invalid argument
and I'm thrown at the Guile promt.
The same problem (well, I think it's the same) was also reported by
roptat on #guix:
https://gnunet.org/bot/log/guix/2017-01-28#T1277485
After bisecting the guix git checkout, I found that commit b1a505baf6¹
was the first one where my system starts to fail. And indeed when I
reverted this commit on the latest master, guix built a working system.
Moreover, the following simple diff (it's a partial revert of that
commit) "fixes" guix for me:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fix-btrfs.diff --]
[-- Type: text/x-diff, Size: 975 bytes --]
diff --git a/gnu/build/file-systems.scm b/gnu/build/file-systems.scm
index 6e5c6aa..f05e035 100644
--- a/gnu/build/file-systems.scm
+++ b/gnu/build/file-systems.scm
@@ -294,15 +294,11 @@ partition field reader that returned a value."
(define %partition-label-readers
(list (partition-field-reader read-ext2-superblock
- ext2-superblock-volume-name)
- (partition-field-reader read-btrfs-superblock
- btrfs-superblock-volume-name)))
+ ext2-superblock-volume-name)))
(define %partition-uuid-readers
(list (partition-field-reader read-ext2-superblock
- ext2-superblock-uuid)
- (partition-field-reader read-btrfs-superblock
- btrfs-superblock-uuid)))
+ ext2-superblock-uuid)))
(define read-partition-label
(cut read-partition-field <> %partition-label-readers))
[-- Attachment #3: Type: text/plain, Size: 407 bytes --]
I don't have btrfs anywhere (only ext4). During bisecting experiments I
used the attached system config (but the config shouldn't matter I think
as I tried various variants, and all gave me the same result).
Any idea how to dig further? Perhaps there is something I can do in the
Guile prompt.
¹ http://git.savannah.gnu.org/cgit/guix.git/commit/?id=b1a505baf61cc771197eb44af9173f31d2bace46
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #4: bare-bones.scm --]
[-- Type: text/x-scheme, Size: 918 bytes --]
(use-modules (gnu))
(operating-system
(host-name "leviafan")
(timezone "Europe/Moscow")
(locale "en_US.utf8")
(bootloader (grub-configuration (device "/dev/sda")))
(initrd (lambda (fs . args)
(apply base-initrd fs
#:extra-modules '("sata_nv") ; for my HDD
args)))
(file-systems (cons (file-system
(device "guix")
(title 'label)
(mount-point "/")
(type "ext4"))
%base-file-systems))
(users (cons (user-account
(name "al")
(group "users")
(supplementary-groups '("wheel" "audio" "video"))
(home-directory "/home/al"))
%base-user-accounts))
(packages %base-packages)
(services (cons* (console-keymap-service "dvorak")
%base-services)))
next reply other threads:[~2017-01-29 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 18:03 Alex Kost [this message]
2017-01-30 9:41 ` bug#25573: Adding btrfs support may break reconfigured system Ludovic Courtès
2017-01-31 17:29 ` Alex Kost
2017-01-31 22:23 ` Ludovic Courtès
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=87wpddzqsz.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=25573@debbugs.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 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).