Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Nov 2023 22:46:54 +0000
From:      bugzilla-noreply@freebsd.org
To:        fs@FreeBSD.org
Subject:   [Bug 275306] 14.0-RELEASE: ossl(4) causes data corruption on encrypted ZFS filesystems/volumes
Message-ID:  <bug-275306-3630-ys4wK2g1cp@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-275306-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-275306-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=3D275306

--- Comment #12 from Daniel Austin <freebsd-ports@dan.me.uk> ---
Created attachment 246620
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D246620&action=
=3Dedit
my loader.conf

I was/am running a generic kernel with ossl.ko loaded via loader.conf.
I've attached my full loader.conf in case anything jumps out at you.

Quite a few things in my loader.conf are no longer needed and are leftover =
from
when the machine was used for a PPPOE gateway for my broadband.  I've just
never got around to removing them.

The panic seemed to trigger after mounting the encrypted filesystems and wh=
en
they had some load applied.  I use them as rsync backup locations so they g=
et a
hit of read then write IO as rsync works out what to copy.

If it is of any help, the hardware is a HP Microserver Gen10 plus with a Xe=
on
E-2224 CPU, 32GB ram, 4 x 4TB SATA drives in a raidz2 configuration and i'm
using a LACP bundle across 2 igb ports (all default lacp settings).
I'm also using bridge to bridge a layer2 openvpn instance to the bundle.

When i originally had the issue, i had 1 error reported in my zpool (even a=
fter
a scrub).  Now I have 3 errors reported across 2 filesystems.

--=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-275306-3630-ys4wK2g1cp>