Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Jan 2017 13:01:36 -0500
From:      Allan Jude <allanjude@freebsd.org>
To:        freebsd-current@freebsd.org
Subject:   Re: zfs zvol's inaccessible after reboot
Message-ID:  <c5985ccd-f66c-9f06-552e-1fa7cc7725af@freebsd.org>
In-Reply-To: <CANJ8om6Mbcsoebxx4LqL2dR%2B9sE0qEGRfjgT9eE4aNkmM2HARA@mail.gmail.com>
References:  <CANJ8om6Mbcsoebxx4LqL2dR%2B9sE0qEGRfjgT9eE4aNkmM2HARA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Lj6dmRU8PH0X907Rjojwl409QTqF6JwPX
Content-Type: multipart/mixed; boundary="XMMvFSpxebhT4hvgn76usnAgVjRL4r6fb";
 protected-headers="v1"
From: Allan Jude <allanjude@freebsd.org>
To: freebsd-current@freebsd.org
Message-ID: <c5985ccd-f66c-9f06-552e-1fa7cc7725af@freebsd.org>
Subject: Re: zfs zvol's inaccessible after reboot
References: <CANJ8om6Mbcsoebxx4LqL2dR+9sE0qEGRfjgT9eE4aNkmM2HARA@mail.gmail.com>
In-Reply-To: <CANJ8om6Mbcsoebxx4LqL2dR+9sE0qEGRfjgT9eE4aNkmM2HARA@mail.gmail.com>

--XMMvFSpxebhT4hvgn76usnAgVjRL4r6fb
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 2017-01-16 12:59, Ultima wrote:
> Currently there is a bug with zvols. I have a few Bhyve containers that=

> startup at boot. I'v noticed in middle December of last year that after=
 a
> restart the zvols become inaccessible to the container. Nothing can be =
done
> to the zvol, other than rename. It cannot even be destroyed in this sta=
te.
> The only way to make it accessible again is to renaming the zvol, after=

> this occurs, functionality is restored.
>=20
> The bug is still present in head r312232.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o=
rg"
>=20

Is this because they are being used by GEOM?

Try: zfs set volmode=3D2 <yourzvol>

Reboot, and see if that solves it

--=20
Allan Jude


--XMMvFSpxebhT4hvgn76usnAgVjRL4r6fb--

--Lj6dmRU8PH0X907Rjojwl409QTqF6JwPX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (MingW32)

iQIcBAEBAgAGBQJYfQqDAAoJEBmVNT4SmAt+wUcP/2yh2O2+3jPHmoDxL6SQgwMT
EzkHamrJhSaawZR6lhOrhREKGdnEwanYn+7eqG00fuFkxyct0OnsdzYzm9VLYAyi
CXRfaWG4hj6GTOrbMwRqG2UlqK67NBhxzZihYBeOGlku5SPK/lS19ivex72jwrgq
7pCTzEhwlSTLJTTwdVcFyWDGChGHPESxoksCpj/q6UStQnrdgCK1oMmS16UC+pca
AxuS4LVG8pc+gVj5fpso4LZyTkEDjNIeiLByxV51xMPgfYVUsX5xNNjHLFIiRfKz
jrpDXTMxIz5g/7y3EoeF3V9dTseWEGJp6MPfxFZhSdVz5dzERUuUHJwdcGILWaW2
thJVanjIH9dyYSs5iJqXoNLqebWuw4LSY93B2dZgnmoQFwl+9tL8jv4pZ8D3ZwtF
QzxZIV3lIyU25/wk0T06m6m02veDilhKKwe9+VPReO2MFEcUeknr2U5374E5SSQm
of6Va3m14RuLJVeEJ+Xy5BLTcxizZ6h6GBsUQHV/QY6QSS2bLgfIzwxYRj2OW9od
45aaiYpCq5AtdweadO6Kmcoyyh3RbT8i0edTIuvDingIidTz9yguXc/4H93IOC5p
JY5YoYdog1zlTBFOfZhlPlXOMbHCNZJi4tw+mloJOxdsFHvYFKNznMLxmhuMLCh4
VMGoMImy4qvPmivxHItx
=8Vv0
-----END PGP SIGNATURE-----

--Lj6dmRU8PH0X907Rjojwl409QTqF6JwPX--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c5985ccd-f66c-9f06-552e-1fa7cc7725af>