This post is more than 5 years old
5 Posts
0
1235
Hyper v cluster setup volume mappings
Hi Guys
I have recently started testing Scaleio. I have found the tutorials and documentation does not really cover the windows install further then bringing a disk online.
my objective is to create clustered shared volumes however I only seem to be able to map a volume to one SDC --sdc_ip or to all SDCs --all_sdcs. I have read that the --all_sdcs switch is not really for Windows -- i get fatal hardware errors from the cluster disks when using this method . I need the volumes to be available to all Failover cluster members but I cannot seem to find the correct way of doing this
any guidance will be greatly appreciated
cmos1
5 Posts
0
June 30th, 2015 03:00
ok and that was it so example as follows:
cli --map_volume_to_sdc --volume_name vol03 --sdc_ip 10.75.132.167 --allow_multi_map
cli --map_volume_to_sdc --volume_name vol03 --sdc_ip 10.75.132.168 --allow_multi_map
this is probably not the fastest way but it works
cmos1
5 Posts
0
June 30th, 2015 00:00
ok got a little further using --allow_multi_map
SanjeevMalhotra
138 Posts
0
June 30th, 2015 03:00
Yes you are correct you have to use -allow_multi_map.
Can you try to unmap the volume and run the following command and check it works?
cli --map_volume_to_sdc --volume_name vol03 --allow_multi_map --all_sdc
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
1
June 30th, 2015 03:00
Hi,
The --all_sdc option is deprecated and shouldn't be used anymore ( I thought we already removed that from the code). You really need to map to each relevant node in your cluster.
The problem with all_sdc is that once you use it, several SCSI persistent reservation commands will simply fail, and this is why you see cluster issues.
Thanks,
Eran
cmos1
5 Posts
0
June 30th, 2015 03:00
Hi,
Tried that did not seem to work
SanjeevMalhotra
138 Posts
0
June 30th, 2015 03:00
scli --map_volume_to_sdc --mdm_ip IP1,IP2 --volume_name vol1 --sdc_ip IP1,IP2,IP3,IP4
Here you can give IP addresses of all the SDCs to which you want the volume to be mapped
becktung0228
5 Posts
0
August 13th, 2015 05:00
Hi All,
I'm a beginner of ScaleIO.
I had tried to map a virtual volume to multiple Hosts for KVM-Based VDI shared-storage purpose and
executed scli commands like below:
[MDM]
> scli --login --username admin --password mypasswd
> scli --add_volume --protection_domain_name default --storage_pool_name default --size_gb 200 --volume_name vol_1
> scli --map_volume_to_sdc --volume_name vol_1 --sdc_ip 192.168.100.10 --allow_multi_map
> scli --map_volume_to_sdc --volume_name vol_1 --sdc_ip 192.168.100.20 --allow_multi_map
[SDC-192.168.100.10: vol_1=>/dev/scinia]
> mkfs.ext4 /dev/scinia
> mkdir /mnt/vm-pool01
> mount /dev/scinia /mnt/vm-pool01
[SDC-192.168.100.20: vol_1=>/dev/scinia]
> mkdir /mnt/vm-pool01
> mount /dev/scinia /mnt/vm-pool01
, however the contains (files) under /mnt/vm-pool01 cannot sync between hosts when some files had been modified on one side! Files that been generated at /mnt/vm-pool01 on Host 192.168.100.10 cannot be listed at 192.168.100.20's /mnt/vm-pool01?
I am confused about the appropriate usage of "--allow_multi_map"!? And i have no idea how to approach the shared-storage major objective?
All suggestions and guidance are welcome.
Many thanks,
Beck
RafaelNovo
92 Posts
0
August 16th, 2015 15:00
start a new thread on this topic, please
becktung0228
5 Posts
0
August 17th, 2015 02:00
Dear Rafa,
I already created a new thread named " How to approach KVM-Based VDI shared-storage scenario with ScaleIO? ".
Thanks for your kind reminder.
Regards,
Beck