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-unsubscr...@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
signature.asc
Description: OpenPGP digital signature
