[Bug 208742] /boot/gptzfsboot boots kernel from another zpool (not root pool)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Apr 13 13:18:02 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208742
--- Comment #10 from Markus Grundmann <markus at freebsduser.eu> ---
No "boofs" is defined. I understand the "issue" when gptzfsboot is using the
first available zpool that holds all files in /boot for first stage of boot.
# zpool import zbackup
# zpool get all zbackup
NAME PROPERTY VALUE SOURCE
zbackup size 7.94G -
zbackup capacity 6% -
zbackup altroot - default
zbackup health ONLINE -
zbackup guid 16990376562684171633 default
zbackup version - default
zbackup bootfs - default
zbackup delegation on default
zbackup autoreplace off default
zbackup cachefile - default
zbackup failmode wait default
zbackup listsnapshots on local
zbackup autoexpand off default
zbackup dedupditto 0 default
zbackup dedupratio 1.00x -
zbackup free 7.40G -
zbackup allocated 550M -
zbackup readonly off -
zbackup comment - default
zbackup expandsize - -
zbackup freeing 0 default
zbackup fragmentation 5% -
zbackup leaked 0 default
zbackup feature at async_destroy enabled local
zbackup feature at empty_bpobj active local
zbackup feature at lz4_compress active local
zbackup feature at multi_vdev_crash_dump enabled local
zbackup feature at spacemap_histogram active local
zbackup feature at enabled_txg active local
zbackup feature at hole_birth active local
zbackup feature at extensible_dataset enabled local
zbackup feature at embedded_data active local
zbackup feature at bookmarks enabled local
zbackup feature at filesystem_limits enabled local
zbackup feature at large_blocks enabled local
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-fs
mailing list