Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Apr 2016 10:11:24 +0200
From:      Fabian Keil <freebsd-listen@fabiankeil.de>
To:        freebsd-fs@freebsd.org
Subject:   Re: GELI + Zpool Scrub Results in GELI Device Destruction (and Later a Corrupt Pool)
Message-ID:  <20160425101124.068c8333@fabiankeil.de>
In-Reply-To: <1461560445.22294.53.camel@michaeleichorn.com>
References:  <1461560445.22294.53.camel@michaeleichorn.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/eNw78W8gnK47rzOSmFw=BpX
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

"Michael B. Eichorn" <ike@michaeleichorn.com> wrote:

> I just ran into something rather unexpected. I have a pool consisting
> of a mirrored pair of geli encrypted partitions on WD Red 3TB disks.
>=20
> The machine is running 10.3-RELEASE, the root zpool was setup with GELI
> encryption from the installer, the pool that is acting up was setup per
> the handbook.
[...]
> I had just noticed that I had failed to enable the zpool scrub periodic
> on this machine. So I began to run zpool scrub by hand. It succeeded
> for the root pool which is also geli encrypted, but when I ran it
> against my primary data pool I encountered:
>=20
> Apr 24 23:18:23 terra kernel: GEOM_ELI: Device ada3p1.eli destroyed.
> Apr 24 23:18:23 terra kernel: GEOM_ELI: Detached ada3p1.eli on last
> close.
> Apr 24 23:18:23 terra kernel: GEOM_ELI: Device ada2p1.eli destroyed.
> Apr 24 23:18:23 terra kernel: GEOM_ELI: Detached ada2p1.eli on last
> close.

Did you attach the devices using geli's -d (auto-detach) flag?

If yes, this is a known issue:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D117158

> And the scrub failed to initialize (command never returned to the
> shell).

This could be the result of another known bug:
https://lists.freebsd.org/pipermail/freebsd-current/2015-October/057988.html

> I immediately rebooted and both disks came back and resilvered, with
> permanent metadata errors

Did those errors appear while resilvering or could they have been
already present before?

Fabian

--Sig_/eNw78W8gnK47rzOSmFw=BpX
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlcd0SwACgkQBYqIVf93VJ0uoQCggfPmGuYbp2v6Bxow312Kw44D
EYgAniwBPf6pKCMayM20gGQCIGGBqEF2
=Q75r
-----END PGP SIGNATURE-----

--Sig_/eNw78W8gnK47rzOSmFw=BpX--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160425101124.068c8333>