so today we experienced some interesting stuff, while extending an imagefile via powershell.
We're using the free version of Starwind VSA on vsphere in a two node scenario.
One Server has 1.82 TB physical Storage available. The starwind VM has two disks assigned, second one holds the image file and has a capacity of 1.77 TB.
We fire the following command, to extend the disk to maximum size:
Code: Select all
$device.ExtendDevice(153600)
Code: Select all
[root@vsan01-a StarWind]# ls -alh storage/mnt/disk1/SST1/
total 1.8T
drwxr-xr-x 2 root root 61 Jul 19 15:02 .
drwxr-xr-x 3 root root 18 Jun 18 21:24 ..
-rw-r--r-- 1 root root 4.0K Jul 19 15:02 SST1_HA.swdsk
-rw-r--r-- 1 root root 1.9T Jul 19 15:33 SST1.img
-rw-r--r-- 1 root root 4.0K Jul 19 15:02 SST1.swdsk
Code: Select all
[root@vsan01-a StarWind]# df -h /mnt/disk1
Filesystem Size Used Avail Use% Mounted on
/dev/sdb 1.8T 1.8T 6.3G 100% /mnt/disk1
So i got two questions:
1) Is it possible to resize the imagefile (note, there was no data written on the new new "available" space yet and if not can we create a smaller image file on server 1 and the sync this to existing second node (This one has the same image sizes, but has 2.2TB Storage available)
2) Shouldn't the powershell api create an error, when there is an attempt to create a larger imagefile then space is available?
Kind regards
martin