[Bug 271113] [zfs][loader] it should be possible to see zpool devices found for loader mountroot stage
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271113] [zfs][loader] it should be possible to see zpool devices found for loader mountroot stage"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 271113] [zfs][loader] it should be possible to see zpool devices found for loader mountroot stage"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 28 Apr 2023 08:40:53 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271113 Bug ID: 271113 Summary: [zfs][loader] it should be possible to see zpool devices found for loader mountroot stage Product: Base System Version: 13.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: dch@freebsd.org If the boot zpool fails to mount early one, this is painful to diagnose, mostly yielding "Error 6" and not much else for a user to deal with. An off-by-default loader tunable that spits out device tasting and zpools it locates would help a lot. No particular reason for it being off-by-default other than on large multi-device pools it could slow down boot a lot if we print out all the things. Specific problem encountered was a zpool where there were traces of a previous zpool on /dev/da0 & /dev/da1 even though the current pool was /dev/da0p3 /devda1p3 both called zroot, and zfs 13.2-RELEASE loader could not decide which one to import. Displaying enumerating each label, pool guid, hostid, hostname, for each device found would be very very useful. zfs: /dev/da1 label2 pool_guid: 1234 hostid: 6788 hostname: 'example.org' zfs: /dev/da1p3 label0 pool_guid: 2345 hostid: 7890 hostname: 'example.net' -- You are receiving this mail because: You are the assignee for the bug.