From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Le Vaillant Subject: bug#38435: BTRFS open_ctree failed Date: Sat, 30 Nov 2019 15:53:11 +0100 Message-ID: <87tv6lo1pk.fsf@yamatai> References: <20191130144539.218179f0@riseup.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:47891) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ib48J-0007Gl-UK for bug-guix@gnu.org; Sat, 30 Nov 2019 09:54:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ib48I-00034D-ST for bug-guix@gnu.org; Sat, 30 Nov 2019 09:54:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:56134) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ib48I-000347-Pf for bug-guix@gnu.org; Sat, 30 Nov 2019 09:54:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ib48I-0002f2-Py for bug-guix@gnu.org; Sat, 30 Nov 2019 09:54:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <20191130144539.218179f0@riseup.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 38435@debbugs.gnu.org raingloom skribis: > This is what I get after a recent `guix system reconfigure` : > Scanning for Btrfs filesystems > [ 2.342790] BTRFS error (device sda1): open_ctree failed > > Previous profiles work, I haven't modified anything about my config.scm > between them. > > [...] > > > Contents of /etc/profile.scm: > > [...] > > (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.