Interesting...
The Microsoft iSCSI initiator showed the correct values - 299.78 and 150 Gigs respectively for the two volumes.
Any suggestions?
Thanks!
Gregg
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.
All the best,
Todd Maxwell
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?
Difference in calculation?
How does Open-e calculate disk.volume size? In other words, how big is a gig?
Thanks!
Gregg
1 kilobyte is equal 1024 bytes and so on.
All the best,
Todd Maxwell
Posting Permissions
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
Forum Rules