Expanding iSCSI ZVol instructions don't work in TrueNAS-SCALE-22.12.2
Description
Problem/Justification
Impact
Activity

Brian Meagher August 16, 2023 at 1:30 PM
Thanks for the bug report. The underlying issue will be fixed in SCALE 23.10 when it becomes available.
In the meantime, there’s a workaround that is completely specific to you; as root in a Linux Shell:

Bug Clerk August 15, 2023 at 10:27 PM

Automation for Jira August 15, 2023 at 10:26 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bug Clerk August 15, 2023 at 10:04 PM

Automation for Jira August 4, 2023 at 7:11 AM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Details
Details
Assignee

Reporter

Confirmed in version TrueNAS-SCALE-22.12.2, updating the size of a ZVol that backs an iSCSI extent does not reflect the size increase to the client connected to given iSCSI LUN. There allegedly was a work-around by editing the comments on the ZVol/Extent and saving would force through the update, but that work-around didn’t work either.
Restarting the TrueNAS server or iSCSI service isn’t an option due to the service interruption to other clients. Online expansions used to work in FreeNAS.
Didn’t see anything in future release notes that this was fixed, but I could have missed it if it did get fixed already.