Date: Tue, 08 Sep 2020 14:44:31 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 249194] New zfs fails to attach on startup on powernv Message-ID: <bug-249194-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249194 Bug ID: 249194 Summary: New zfs fails to attach on startup on powernv Product: Base System Version: CURRENT Hardware: powerpc OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: jhibbits@FreeBSD.org The zpool rc.d script runs before mountcritlocal now, with the new OpenZFS import. However, powernv (powerpc64 native on IBM hardware) puts /boot on a separate filesystem, which doesn't get mounted until after that point. This causes the zpool script to fail if zfs is not built into the kernel. This appears to have been fine before because zfs(8) would automagically import the pool when starting up (after mountcritlocal, required by zfsbe), but zpools don't get automatically imported anymore. A hack to workaround this I did was to add a '/etc/rc.d/zpool start' into the two startup blocks in /etc/rc.d/zfs, but that's probably the wrong solution. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-249194-227>