From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#37977: Mount options ignored for root file system Date: Sun, 17 Nov 2019 11:43:39 +0100 Message-ID: <87bltapyuc.fsf@gnu.org> References: <87pnif6ec0.fsf@yamatai> <87eeyjils5.fsf@yamatai> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36774) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iWI2F-000417-M0 for bug-guix@gnu.org; Sun, 17 Nov 2019 05:44:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iWI2E-0007Rb-P0 for bug-guix@gnu.org; Sun, 17 Nov 2019 05:44:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:59795) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iWI2E-0007RV-M2 for bug-guix@gnu.org; Sun, 17 Nov 2019 05:44:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iWI2E-0006J4-HD for bug-guix@gnu.org; Sun, 17 Nov 2019 05:44:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87eeyjils5.fsf@yamatai> (Guillaume Le Vaillant's message of "Thu, 07 Nov 2019 19:28:10 +0100") 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: Guillaume Le Vaillant Cc: 37977@debbugs.gnu.org Hi Guillaume, Guillaume Le Vaillant skribis: > Guillaume Le Vaillant skribis: > >> The filesystem options declared for the root file system are apparently >> ignored. This happens for a btrfs root filesystem on a LUKS volume. > > This also happens on a basic btrfs root file system (without LUKS). > > I tried adding "rootflags=3Ddefaults,autodefrag,compress=3Dlzo" in kernel > arguments, but it didn't have any effect. [...] > I saw that the 'start' function of 'root-file-system-service-type' > doesn't do anything. Is it on purpose? Or could we make it remount the > root filesystem? By definition, when shepherd is started, the root file system is already mounted; that=E2=80=99s why the =E2=80=98start=E2=80=99 method of the =E2= =80=98root-file-system-service=E2=80=99 does nothing. The root file system is mounted by =E2=80=98mount-root-file-system=E2=80=99= in linux-boot.scm, and you=E2=80=99re right: it happily ignores any options in= the object for =E2=80=9C/=E2=80=9D. :-) A solution would be to have =E2=80=98boot-system=E2=80=99 take an additional #:root-file-system-options parameter that it would pass down to =E2=80=98mount-root-file-system=E2=80=99, which would honor it. Would you like to give it a try? Thanks, Ludo=E2=80=99.