Date: Fri, 26 Feb 2021 11:40:32 +0100 From: infoomatic <infoomatic@gmx.at> To: freebsd-fs@freebsd.org Subject: Re: FreeBSD 13 BETA3 zfs mount failed Message-ID: <3ffea3bf-a9f9-dfe5-d835-1874da1141e5@gmx.at> In-Reply-To: <47e949d3-2fc4-f581-e8a8-a707a23406ab@gmx.at> References: <92cd2855-8765-234e-3763-3811da269704@gmx.at> <f1221ad8-61c8-f2e9-2faf-2c6e910403b0@FreeBSD.org> <47e949d3-2fc4-f581-e8a8-a707a23406ab@gmx.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26.02.21 09:56, infoomatic wrote: > Another scenario: I did the same setup as in my previous mail on BETA3, > sent some snapshots to the encrypted dataset on BETA3. I then could > however import the the pool in Linux as read-only (feature > com.delphix:log_spacemap was missing), could also load-key and read the > encrypted dataset. interestingly, importing the pool read-only on linux destroyed some metadata. The pool cannot be imported in BETA3 any more: [root@blackbox ~]# zpool import =C2=A0=C2=A0 pool: hd012 =C2=A0=C2=A0=C2=A0=C2=A0 id: 16225333054044272411 =C2=A0 state: FAULTED status: The pool metadata is corrupted. =C2=A0action: The pool cannot be imported due to damaged devices or data. =C2=A0=C2=A0 see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-72 =C2=A0config: =C2=A0=C2=A0=C2=A0 hd012=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 FAULTED=C2=A0= corrupted data =C2=A0=C2=A0=C2=A0 =C2=A0 da0s1=C2=A0=C2=A0=C2=A0=C2=A0 ONLINE [root@blackbox ~]# zpool import -f hd012 cannot import 'hd012': one or more devices is currently unavailable [root@blackbox ~]# zpool status -v hd012 cannot open 'hd012': no such pool I will do some more tests and will report here.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ffea3bf-a9f9-dfe5-d835-1874da1141e5>