From owner-freebsd-current@freebsd.org Tue Apr 9 08:42:51 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2B0C1579EC8 for ; Tue, 9 Apr 2019 08:42:51 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1ADEE833C7 for ; Tue, 9 Apr 2019 08:42:51 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTP id x398glIk050737 for ; Tue, 9 Apr 2019 10:42:47 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id x398glUo050734 for ; Tue, 9 Apr 2019 10:42:47 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Tue, 9 Apr 2019 10:42:47 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD CURRENT Subject: Re: r346025: ZFS filesystems do not mount anymore In-Reply-To: Message-ID: References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 08:42:51 -0000 On Tue, 9 Apr 2019 10:06+0200, Trond Endrestøl wrote: > On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > Hello, > > > > after a bunch of updates this weekend, mounting ZFS filesystems on CURRENT r346025 doesn't > > work anymore at boot time when ZFS is built-in-kernel. zfs_enable="YES" is set in /etc/rc.conf. > > > > After the system has booted, mounting all ZFS filesystems via "zfs mount -a" operates as > > expected and all filesystems are available as usual. > > I blame r346017: > > Trying to mount root from zfs:zroot/ROOT/20190409-r346017 [] > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > Setting hostid: 0xf9071336. > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > Starting file system checks: > Mounting local filesystems:. > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > ELF ldconfig path: /lib /usr/lib /usr/lib/compat > 32-bit compatibility ldconfig path: /usr/lib32 > > [...] > > Creating and/or trimming log files. > Starting syslogd. > Apr 9 09:48:32 freebsd-head-zfs syslogd: /var/log/security: No such file or directory > Setting date via ntp. > 9 Apr 09:48:38 ntpdate[1073]: step time server 2001:W:X:Y::Z offset -0.992370 sec > No core dumps found. > Clearing /tmp (X related). > Updating motd:. > Mounting late filesystems:mount: /usr/compat/linux: No such file or directory > mount: /usr/compat/linux: No such file or directory > mount: /usr/compat/linux: No such file or directory > mount: /usr/compat/linux: No such file or directory > . > Mounting /etc/fstab filesystems failed, startup aborted > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > Enter full pathname of shell or RETURN for /bin/sh: > root@freebsd-head-zfs:/ # zfs mount -av > root@freebsd-head-zfs:/ # mount -al > root@freebsd-head-zfs:/ # exit > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > Setting hostid: 0xf9071336. > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > Fast boot: skipping disk checks. > Mounting local filesystems:. > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > interface zfsctrl.1 already present in the KLD 'kernel'! > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > kldload: an error occurred while loading module zfs. Please check dmesg(8) for more details. > /etc/rc: WARNING: Unable to load kernel module zfs > ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.28/mach/CORE > 32-bit compatibility ldconfig path: /usr/lib32 > > [...] At a later point, this happens: Starting syslogd. usage: protect [-i] command protect [-cdi] -g pgrp | -p pid Setting date via ntp. It looks like syslogd is no longer protected against the OOM killer. > Once I manually mount the remaining filesystems, multiuser boot > proceeds as expected. My kernel has options ZFS, and the boot scripts > doesn't account for this scenario. -- Trond. From owner-freebsd-current@freebsd.org Tue Apr 9 13:31:38 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F4001581329 for ; Tue, 9 Apr 2019 13:31:38 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B3668D693 for ; Tue, 9 Apr 2019 13:31:37 +0000 (UTC) (envelope-from ohartmann@walstatt.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1554816620; bh=UntC4PAh1wgBVc+Z3L7kx/8qbrgHIt41UHi6X7qTpRo=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References; b=dYQJ5r7CZc0ugEHtQaDJ19KOzjDCSeEPEgVNvCak0artKDbjb+OnQx2CJP63enAy1 yOv1hvjevqjrB8S8Vr/UDBXDQIk4lKqhtHhIFZglQtDEiXlMdZL8YM0B44jSlmCy3W r4rKsdA/2uVBUKduBBom1otq7Iis2zX8xmtq042A= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from freyja ([46.88.91.252]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LaFmY-1gSzD80nGA-00m6FW; Tue, 09 Apr 2019 15:30:20 +0200 Date: Tue, 9 Apr 2019 15:30:18 +0200 From: "O. Hartmann" To: Trond =?ISO-8859-1?Q?Endrest=F8l?= Cc: FreeBSD CURRENT Subject: Re: r346025: ZFS filesystems do not mount anymore Message-ID: <20190409153014.5299494e@freyja> In-Reply-To: References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:k/zU48DkXdCAFVAr8Z3KXOK3VGJiZEyf8UWJDCbQksBiqL+Mk+z k/5PAeAFxLwFrJ3mYS33sOKybHiRx4Za8wxthOV7z+F5/ewmgGmc2TDRb5FiC2me0Kj3e/R Elrw0KEhvxpjJCqBrijuPkxGbGvS2tosupfbg0zkLcnrMvXoLGPuk08Be9RjUU9mPvqP0FC jhDzbyYWieqRwDq/oQI/Q== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:IEzv/CFQXtE=:qefXOQe1SsaAMMCTSsTdPO w/T7qNhKfZOZrnBsZ+XabZo/rs/7U4/ETMyC0JfYWnKS+qyjfskjdxMXu5oR72oNEID/xsDFb 7A16CMm4OZDiZU/SP+057v9sDC0TVxKVMA4+mIbnvRMeyAETK7oJfu5KPIRzuoBqm7CYydZ01 JwcYXon/u3CdfNioC7ZKmfid877ihFDqDh+BDhBr43ILHbCUmfiMH9zFgYwT8kocsAc02LENv P3cLPFPUvv7QNNnpR69fIKzUYDWKbjgep4kG/hnTDXSjp8CnN6Ollk5kbUO46TfotdV6bgNUg UgoWZm8T3JnpSQePluEIrcyqWsZfiFNxHJXYOSPUfWM2p7dzleLuGZFIQ4CSguQ4feaDQgQJ2 0EcQ1ugqEQ4Xyn9CtlU9zwJnbaTinhA6k8eb6ZacAirqqimhylP4QQmTLFO8Q592u0h2O7Qzw oPxlTRbEF1oNwZmmEMdAo+GX05myEZIdPNcSs8rQB0YgFLQAHgFnBevTGT4JVSdIe1QaFtQ7p Q3glTGfm91niq1EJQIFf2RXogz2Pe0ZGSKtP17gHI2ctppsk84KV8EFwWTfaLtyIUotbyp9m1 t9yWZTiVyTisF1r6fV5NEQRuuSKRu6AhTUxhbYVJxw9f+y5/wjBYN0haOTFQaUglHxRjW+nTi 7hCtM9VhqufBPM78WrAI4GTeNZuLwOmbx0/SwhReoLhiSDmXVFKxum2nhlYK1Q1SB9txgO375 EmB2joQLh0ABhQstKIenHU0US5vH/q7dDXmCWUUJpLhkooS9bSm5W+952aD4uEXQFhNwvHxFO FMv84K/NBnoE41+/1jtHp5ue32HMHE6APup+jJ4GSqSVV9W71slIwNJettiJVvAEsFapoGgYT yVFZvBCrc7R34MIpzMAR0NHQRgksEsr70m8vh3UVobMN9ab0er6jVVSZQnAwI8gWA01RRjvaS yhwslpt5n+Q== X-Rspamd-Queue-Id: 9B3668D693 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 13:31:38 -0000 On Tue, 9 Apr 2019 10:42:47 +0200 (CEST) Trond Endrest=F8l wrote: > On Tue, 9 Apr 2019 10:06+0200, Trond Endrest=F8l wrote: >=20 > > On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote: > > =20 > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA256 > > >=20 > > > Hello, > > >=20 > > > after a bunch of updates this weekend, mounting ZFS filesystems on > > > CURRENT r346025 doesn't work anymore at boot time when ZFS is > > > built-in-kernel. zfs_enable=3D"YES" is set in /etc/rc.conf. > > >=20 > > > After the system has booted, mounting all ZFS filesystems via "zfs mo= unt > > > -a" operates as expected and all filesystems are available as usual. = =20 > >=20 > > I blame r346017: > >=20 > > Trying to mount root from zfs:zroot/ROOT/20190409-r346017 [] > > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > > Setting hostid: 0xf9071336. > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > Starting file system checks: > > Mounting local filesystems:. > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > ELF ldconfig path: /lib /usr/lib /usr/lib/compat > > 32-bit compatibility ldconfig path: /usr/lib32 > >=20 > > [...] > >=20 > > Creating and/or trimming log files. > > Starting syslogd. > > Apr 9 09:48:32 freebsd-head-zfs syslogd: /var/log/securit= y: > > No such file or directory Setting date via ntp. > > 9 Apr 09:48:38 ntpdate[1073]: step time server 2001:W:X:Y::Z offset > > -0.992370 sec No core dumps found. > > Clearing /tmp (X related). > > Updating motd:. > > Mounting late filesystems:mount: /usr/compat/linux: No such file or > > directory mount: /usr/compat/linux: No such file or directory > > mount: /usr/compat/linux: No such file or directory > > mount: /usr/compat/linux: No such file or directory > > . > > Mounting /etc/fstab filesystems failed, startup aborted > > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > > Enter full pathname of shell or RETURN for /bin/sh: > > root@freebsd-head-zfs:/ # zfs mount -av > > root@freebsd-head-zfs:/ # mount -al > > root@freebsd-head-zfs:/ # exit > > Setting hostuuid: 7b624d1c-4bc3-e2cb-4ac2-6487a4b4774c. > > Setting hostid: 0xf9071336. > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > Fast boot: skipping disk checks. > > Mounting local filesystems:. > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > interface zfsctrl.1 already present in the KLD 'kernel'! > > linker_load_file: /boot/kernel/zfs.ko - unsupported file type > > kldload: an error occurred while loading module zfs. Please check dmesg= (8) > > for more details. /etc/rc: WARNING: Unable to load kernel module zfs > > ELF ldconfig > > path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compa= t/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.28/mach/CORE > > 32-bit compatibility ldconfig path: /usr/lib32 > >=20 > > [...] =20 >=20 > At a later point, this happens: >=20 > Starting syslogd. > usage: protect [-i] command > protect [-cdi] -g pgrp | -p pid > Setting date via ntp. >=20 > It looks like syslogd is no longer protected against the OOM killer. >=20 > > Once I manually mount the remaining filesystems, multiuser boot=20 > > proceeds as expected. My kernel has options ZFS, and the boot scripts=20 > > doesn't account for this scenario. =20 >=20 >=20 Hello, thank you for investigating! I think you're correct. I was wondering how th= is change could make it into the tree with this kind of impact. Maybe filing a PR would be fine? Kind regards, oh