Date: Mon, 16 Jan 2017 13:24:09 -0500 From: Ultima <ultima1252@gmail.com> To: Allan Jude <allanjude@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: zfs zvol's inaccessible after reboot Message-ID: <CANJ8om45emptPMXfTqw8ho1dySMXMQwixmuq0ampsLw1TZxUmw@mail.gmail.com> In-Reply-To: <c5985ccd-f66c-9f06-552e-1fa7cc7725af@freebsd.org> References: <CANJ8om6Mbcsoebxx4LqL2dR%2B9sE0qEGRfjgT9eE4aNkmM2HARA@mail.gmail.com> <c5985ccd-f66c-9f06-552e-1fa7cc7725af@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The volmode was set to default, which is geom. Setting to 2, dev fixes the issue! thanks Allan for the speedy solution! On Mon, Jan 16, 2017 at 1:01 PM, Allan Jude <allanjude@freebsd.org> wrote: > 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 > state. > > The only way to make it accessible again is to renaming the zvol, after > > this occurs, functionality is restored. > > > > 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.org" > > > > Is this because they are being used by GEOM? > > Try: zfs set volmode=2 <yourzvol> > > Reboot, and see if that solves it > > -- > Allan Jude > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANJ8om45emptPMXfTqw8ho1dySMXMQwixmuq0ampsLw1TZxUmw>