Bug 249194 - New zfs fails to attach on startup on powernv
Summary: New zfs fails to attach on startup on powernv
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: powerpc Any
: --- Affects Only Me
Assignee: freebsd-fs (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2020-09-08 14:44 UTC by Justin Hibbits
Modified: 2020-09-30 00:21 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Hibbits freebsd_committer freebsd_triage 2020-09-08 14:44:31 UTC
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.
Comment 1 Ryan Moeller freebsd_committer freebsd_triage 2020-09-30 00:21:01 UTC
Is this still an issue after r365348 changed the order?