Date: Tue, 9 Apr 2019 21:51:12 -0700 From: Enji Cooper <yaneurabeya@gmail.com> To: Michael Butler <imb@protected-networks.net> Cc: "O. Hartmann" <ohartmann@walstatt.org>, =?utf-8?Q?Trond_Endrest=C3=B8l?= <Trond.Endrestol@fagskolen.gjovik.no>, FreeBSD CURRENT <freebsd-current@freebsd.org>, crees@freebsd.org Subject: Re: r346025: ZFS filesystems do not mount anymore Message-ID: <4422B7AB-B398-472B-9F66-00624853EE3D@gmail.com> In-Reply-To: <5c2f7554-5da2-e55b-4918-c7174fc091fe@protected-networks.net> References: <20190408195800.37046b3c@thor.intern.walstatt.dynvpn.de> <alpine.BSF.2.21.9999.1904091002450.81396@mail.fig.ol.no> <alpine.BSF.2.21.9999.1904091011410.81396@mail.fig.ol.no> <20190409153014.5299494e@freyja> <5c2f7554-5da2-e55b-4918-c7174fc091fe@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Apr 9, 2019, at 18:29, Michael Butler <imb@protected-networks.net> wrot= e: >=20 >> On 2019-04-09 09:30, O. Hartmann wrote: >> On Tue, 9 Apr 2019 10:42:47 +0200 (CEST) >> Trond Endrest=C3=B8l <Trond.Endrestol@fagskolen.gjovik.no> wrote: >>=20 >>>> On Tue, 9 Apr 2019 10:06+0200, Trond Endrest=C3=B8l 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 mou= nt >>>>> -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 <kern.emerg> 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 >>=20 >> Hello, >>=20 >> thank you for investigating! I think you're correct. I was wondering how t= his >> change could make it into the tree with this kind of impact. >>=20 >> Maybe filing a PR would be fine? >>=20 >=20 > 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: >=20 > a single-user boot > mount -a > mount -u -o rw / > zfs mount -a >=20 > Reverting this change restores normal operation at start-up. >=20 > ZFS is also compiled into the kernel on my system, >=20 > imb CCing crees@, the author of r346017, for context. I will file a PR soon if o= ne hasn=E2=80=99t already been filed. -Enji=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4422B7AB-B398-472B-9F66-00624853EE3D>