https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192085
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org
Ke
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192085
Kristof Provost changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192085
Chloé Desoutter changed:
What|Removed |Added
CC||chloe.desout...@atasta.net
--- C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192085
--- Comment #3 from Kristof Provost ---
Created attachment 144931
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144931&action=edit
zvol resize patch
This patch fixes the problem for me, but it might be better to import all of
3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192085
--- Comment #2 from Kristof Provost ---
The problem appear to be fixed in Illumos commit
3b2aab18808792cbd248a12f1edf139b89833c13
Essentially they've changed from using dmu_objset_hold() to
dmu_objset_own().
See:
- https://www.illumos.or
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192085
--- Comment #1 from Kristof Provost ---
I've poked at this a bit more, and I think I understand the problem now.
zvol_set_volsize() takes a hold on the file system with dmu_objset_hold()
and then verifies that it's not marked as read-only.
