Bug 229628
| Summary: | Can't import bootpool in ZFS installation with installerconfig | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Kazuhiko Kiriyama <kiri> | ||||
| Component: | misc | Assignee: | freebsd-sysinstall (Nobody) <sysinstall> | ||||
| Status: | New --- | ||||||
| Severity: | Affects Many People | CC: | dteske, imp | ||||
| Priority: | --- | Keywords: | patch | ||||
| Version: | CURRENT | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Add a couple of reviewers who work in this area. |
Created attachment 194980 [details] bsdinstall,zfsboot and script patch of 12.0-CURRENT-r335317 In bsdinstall using installerconfig, if you divide the ZFS file system into bootpool and zroot, there are the following problems. (1) Since /boot is symbolically linked to /bootpool, it is expanded by tar - xf distrubution_tarball - C chroot_directory in script so it will not be expanded to /bootpool. This can be solved by adding the -P option to tar. (2) bootpool's zpool.cache information does not contain bootpool information and zroot's zpool.cache does not exist, bootpool will not be imported at boot time and will not boot properly. To solve this problem create zpool.cache with bootpool and zroot in /boot/zfs/zpool.cache with zpsboot on bootpool after creating bootpool, and on zroot as well zpool.cache in /boot/zfs/zpool.cache. If you try to output debugging information to the display and the file at the same time, it will not be output to the specified file normally . This is because tee does not have the -a option in bsdinstall.