Date: Sun, 14 Feb 2016 13:07:59 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 207188] gptzfsboot may choose wrong pool Message-ID: <bug-207188-8@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207188 Bug ID: 207188 Summary: gptzfsboot may choose wrong pool Product: Base System Version: 10.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: matthias.pfaller@familie-pfaller.de Created attachment 166981 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166981&action=edit output of zpool and gpart commands I'm using five disks in my system (ada0, ada1 and ada4 are SSDs, ada2 and ada3 conventional disks). ada2, ada3 and ada4 hold one freebsd-zfs partition each. ada2 and ada3 contain the data and ada4 is used for L2ARC. ada0 and ada1 hold two freebsd-zfs partitions each. Partition one on each disk is used for a mirrored intent log for the data pool. Partition two holds the mirrored root pool. I have set the bootfs property on the pool root but not on the pool data. gptzfsboot tries to load data/boot/gptzfsloader (and fails). It fails even when there you put zfsloader into data/boot. After reordering the GPT entries the system boots fine. I think this behaviour should be documented in gptzfsboot(8). The attached was done with the reordered gpt. -- 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-207188-8>