Date: Tue, 16 Mar 2021 21:46:18 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 254349] cannot set bootfs on pool after removing a vdev Message-ID: <bug-254349-3630-g9VeU8xPVc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254349-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-254349-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254349 --- Comment #3 from Martin Matuska <mm@FreeBSD.org> --- It looks like VDEV_TYPE_INDIRECT is handled at stand/libsa/zfs/zfsimpl.c The code originates in the device removal feature: https://github.com/openzfs/zfs/commit/a1d477c24c7badc89c60955995fd84d311938= 486 By modifying the vdev_is_bootable() function, setting bootfs is not allowed anymore. I think this is an easy fix and really not necessary on FreeBSD. Thomas Soome has been dealing with support of indirect vdevs at end of 2019, see: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D355786 It would be great if Thomas would tell us some more about the support of removed vdevs (=3Dindirect vdevs). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254349-3630-g9VeU8xPVc>