locked Dataset shown as "unlocked" after upgrade vom Angelfish

[Mark St.]

dataset is a encrypted zvol, used for a virtual machine

virtual machine was set to autostart (doesnt work with encrypted zvol but didnt cause a problem before bluefin)

after reboot, the dataset is shown as "unlocked" in the gui..."lock" function doesnt work ("dataset is locked")

after unchecking autostart for the virtual machine and a reboot, everything is ok, dataset i shown as locked

 

[morganL]

If the problem was not there for angelfish and you can reproduce, please report a bug with the details.

 

[billxsand]

Having the exact same issue

 

[kiler129]

I'm seeing the same behavior for encrypted zvols - after reboot they show as unlocked but they're in fact locked. @billxsand did you create issue on Jira maybe?

Found the Jira ticket and a fix: https://ixsystems.atlassian.net/browse/NAS-119410#icft=NAS-119410

As a temporary measure it's possible to unlock the zvol with "zfs load-key pool-name/zvol". It shouldn't be done around the GUI because the GUI will *not* know about this. However, in this case it makes sense as middleware thinks it's unlocked anyway.