Is it safe (non-destructive, non-corruptive) to grow a file extent based iSCSI LUN by simply increasing the value of "Extent Size" from Sharing -> Block (iSCSI) -> Extents?
I did a quick test by bumping up a file extent from 50GB to 500GB and FN increased the underlying file to 500GB. My VMware host saw the new LUN size after a scan and I was able to in crease the VMFS without any issues.
FN documentation says to use truncate command line on the file extent itself and then setting the extent size to 0 (auto), but then I lose the ability to view the size of my LUNs from the webGUI.
Why is the WebGUI method not the preferred method? Just seems easier and I can still see the LUN size.
I did a quick test by bumping up a file extent from 50GB to 500GB and FN increased the underlying file to 500GB. My VMware host saw the new LUN size after a scan and I was able to in crease the VMFS without any issues.
FN documentation says to use truncate command line on the file extent itself and then setting the extent size to 0 (auto), but then I lose the ability to view the size of my LUNs from the webGUI.
Why is the WebGUI method not the preferred method? Just seems easier and I can still see the LUN size.