Getting zfs exception when resizing due to incompatible size to to volblocksize about linstor-server

[ghernadi]

Thanks for the report, we are aware of this issue with newer ZFS versions and are already working on a fix for this issue.

In order to get LINSTOR out of the resizing state, I'd suggest the following steps:

• Resize ZFS by hand:
  That means, take the command from the ErrorReport, add 8k to the size so it is a multiple of 16k and run the command manually on the node (or all nodes) that reported this error.
• (Optional) Find out the exact size of the VD so that the next command does not additionally grow your VD:
  This step is obviously only needed if you are unsure about the exact size of your VD. If you have just resized your VD to for example 100GiB, feel free to skip this step and use the very same size argument again in the next step.
  To find out the exact size of a VD is to check linstor -m vd l -r $rsc_name and look for volume_definitions[$your_vlm_nr].size_kib. If you have jq installed and only have a single VD for the given resource, you could use something like this:
  linstor -m vd l -r $rsc_name | jq '.[0][0].volume_definitions[0].size_kib'.
  If you are using this method, please make sure to also properly use the KiB suffix for the size in the next step.
• Re-run the linstor vd size ... command.
  This should make LINSTOR find the ZFS volume is already in the expected state, resize DRBD (if needed) and properly finish the resize operation by removing the flags from the VD.

[dniasoff]

Thanks for a detailed and helpful response.

For now I have configured the storage pool to use a volblocksize of 4k which seems to solve the problem. I am guessing this might have an impact on disk usage/performance so look forward to the fix. This means any volumes already created before the fix will be stuck with a 4k volblocksize.