Weird disk sizes in Virtuall Iron

[To-M]

I have not seen this issue before where the size is larger then what was created. Seeing that you tested with both File and Block IO I can't imagine how it would increase the values.

Does this happen if you test with just a Microsoft system using the MS iSCSI initiator?

[gregg_hughes]

The Microsoft iSCSI initiator showed the correct values - 299.78 and 150 Gigs respectively for the two volumes.

Any suggestions?

Thanks!


Gregg

[To-M]

Not sure why as well. Unless there is a Virtual Iron initiator setting that you can match with ours. You can go to the console and enter CTRL + ALT + W then Tuning options then iSCSI daemon options then select the Target and compare with Virtual Iron.

[enealDC]

Well I have 3 Open-E systems (2DSS and 1 ISCSIR3) deployed for VI and I've never seen this issue. It's truly weird.

In /opt/VirtualIron/VirtualizationManager/system/logs/node.ip.address.log - what are the reported sizes for the disks there?

Do you mind emailing me your logs file from Open-E and log files from running getSupportInfo.py on Virtual Iron?

[gregg_hughes]

How does Open-e calculate disk.volume size? In other words, how big is a gig?

Thanks!


Gregg

[To-M]

1 kilobyte is equal 1024 bytes and so on.