Date: Thu, 18 Apr 2024 10:09:16 -0400 From: mike tancsa <mike@sentex.net> To: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: zfs boot error on mirrored drive Message-ID: <0c069bca-b512-457b-8934-66b859f449db@sentex.net> In-Reply-To: <d17afa19-f563-450e-ac95-11c1d152e5fb@quip.cz> References: <82761f2b-475f-43ab-b045-95c60c330db7@sentex.net> <d17afa19-f563-450e-ac95-11c1d152e5fb@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/18/2024 10:04 AM, Miroslav Lachman wrote: > I am not a ZFS expert but can this be stored in a > /etc/zfs/zpool.cache? (or in a different path, I remember zpool.cache > was stored somewhere else in older versions of FreeBSD, maybe > /boot/zfs/zpool.cache) > You can try to delete zpool.cache (just rename so you can move it > back), import and export should re-create it. > I dont have one in /etc just in /boot/zfs. Doing a strings on that file, I dont see reference to zbackup1 however, just the real pool, zroot. So strange. I am guessing its stored somewhere specifically on the individual drives? # strings /boot/zfs/zpool.cache zroot version name zroot state pool_guid hostid hostname nanobsd2.sentex.ca com.delphix:has_per_vdev_zaps vdev_children vdev_tree type root guid children type mirror guid metaslab_array metaslab_shift ashift asize is_log create_txg com.delphix:vdev_zap_top children type disk guid path /dev/ada0p3 phys_path id1,enc@n3061686369656d30/type@0/slot@1/elmdesc@Slot_00/p3 whole_disk create_txg com.delphix:vdev_zap_leaf type disk guid path /dev/ada1p3 phys_path id1,enc@n3061686369656d30/type@0/slot@2/elmdesc@Slot_01/p3 whole_disk create_txg com.delphix:vdev_zap_leaf features_for_read com.delphix:hole_birth com.delphix:embedded_data
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0c069bca-b512-457b-8934-66b859f449db>