From owner-freebsd-current@freebsd.org Wed Apr 10 01:29:24 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 C90D7157424F for ; Wed, 10 Apr 2019 01:29:24 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 616048A175 for ; Wed, 10 Apr 2019 01:29:22 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1554859753; bh=9Wd79zpx OLxyotqi1kPOSPcP44abn1zIpO+/Afz34HM=; b=O9LtDVwbk1RCsBQzA/7onmVr aX+Qfl/XucMXmGb5e9k3L9EqqAHe5HL/nRi5q34zwN7QmWnNlzCaF88rYjYuxBFf 066peknbgRNlXgrYXXEBQJ+d39sw1Xhui346tlR91pgaqd5GJKCbVbKdK4FYHHhE Oy8/zzYl8rhEpCXpMjA= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 22879F20E; Tue, 9 Apr 2019 21:29:13 -0400 (EDT) Subject: Re: r346025: ZFS filesystems do not mount anymore To: "O. Hartmann" , =?UTF-8?Q?Trond_Endrest=c3=b8l?= Cc: FreeBSD CURRENT References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> <20190409153014.5299494e@freyja> From: Michael Butler Openpgp: preference=signencrypt Message-ID: <5c2f7554-5da2-e55b-4918-c7174fc091fe@protected-networks.net> Date: Tue, 9 Apr 2019 21:29:12 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190409153014.5299494e@freyja> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 616048A175 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protected-networks.net header.s=201508 header.b=O9LtDVwb; spf=pass (mx1.freebsd.org: domain of imb@protected-networks.net designates 202.12.127.228 as permitted sender) smtp.mailfrom=imb@protected-networks.net X-Spamd-Result: default: False [-1.58 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[protected-networks.net:+]; MX_GOOD(-0.01)[sarah.protected-networks.net,mail.protected-networks.net]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.01)[country: US(-0.06)]; ASN(0.00)[asn:5716, ipnet:202.12.127.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.66)[-0.664,0]; R_DKIM_ALLOW(-0.20)[protected-networks.net:s=201508]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.61)[0.607,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[protected-networks.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] 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: Wed, 10 Apr 2019 01:29:25 -0000 On 2019-04-09 09:30, O. Hartmann wrote: > On Tue, 9 Apr 2019 10:42:47 +0200 (CEST) > Trond Endrestøl wrote: > >> 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. >> >> > > Hello, > > thank you for investigating! I think you're correct. I was wondering how this > change could make it into the tree with this kind of impact. > > Maybe filing a PR would be fine? > I just confirmed that the change at SVN r346017 after 'mergemaster -U' yields a (ZFS-based) system which can only be brought into normal service through: a single-user boot mount -a mount -u -o rw / zfs mount -a Reverting this change restores normal operation at start-up. ZFS is also compiled into the kernel on my system, imb