Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Feb 2021 13:57:44 +0100
From:      infoomatic <infoomatic@gmx.at>
To:        freebsd-fs@freebsd.org
Subject:   Re: FreeBSD 13 BETA3 zfs mount failed
Message-ID:  <3c82d04f-e5d3-5bf4-df16-9995b95fc925@gmx.at>
In-Reply-To: <92cd2855-8765-234e-3763-3811da269704@gmx.at>
References:  <92cd2855-8765-234e-3763-3811da269704@gmx.at>

next in thread | previous in thread | raw e-mail | index | archive | help
some more info:

The FreeBSD 13 BETA3 box I tried to use the zpool has a "CPU: Intel(R)
Celeron(R) CPU=C2=A0 J1900=C2=A0 @ 1.99GHz (2000.05-MHz K8-class CPU)" wit=
hout
hardware encryption module.

So I stumbled upon Bug 252981 from the last days and tried the patch
from markj (openzfs-master e7adccf7f commit) that disables

the use of hardware crypto offload drivers, however, the result is the sam=
e.


On 25.02.21 01:25, infoomatic wrote:
> Hi,
>
> I am sharing my photos via an external hard drive with my family
> members. I use bhyve+pass-through of the device to access it on ZFS via
> a Linux VM (the others use Linux).
>
> I wanted to get rid of bhyve, so gave BETA3 a try. Created the partition
> on Ubuntu 20.04 Linux and made a zpool "hd015" (kernel 5.4.0-66-generic,
> zfsutils-linux 0.8.3-1ubuntu12.6), encrypted the dataset hd015/fotos,
> created some datasets beneath and copied some photos over.
>
> On a FreeBSD 13 BETA3 box, I did a "zfs load-key hd015/fotos", however,
> a "zfs mount -a" resulted in:
>
> cannot mount 'hd015/fotos/2018-2019-weltreise': mount failed
> cannot mount 'hd015/fotos/2018-2019-weltreise': mount failed
> cannot mount 'hd015/fotos/2016': Input/output error
> cannot mount 'hd015/fotos/2021': Input/output error
> cannot mount 'hd015/fotos/2011': Input/output error
>
>
> "zpool status -v hd015" gives:
>
> ...
>
> errors: Permanent errors have been detected in the following files:
>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hd015/fotos/2021:<0x0>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hd015/fotos/2011:<0x0>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hd015/fotos/2016:<0x0>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hd015/fotos/2020:<0x0>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hd015/fotos/2018-2019-weltrei=
se:<0x0>
>
> I assume this is not expected behaviour, and I am willing to help to
> resolve this ... any info/direction/tasks to debug is welcome, thanks!
>
> Robert
>
>
> _______________________________________________
> freebsd-fs@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c82d04f-e5d3-5bf4-df16-9995b95fc925>