How to mount S-VOLs on Windows Servers
The following is a small synopsis of the steps that you will need to follow when scripting HUR/TC/SI/CoW operations using CCI on Windows. Without using all of these steps, you will have one problem or another - disappearing data or filesystems that appear "corrupt" from a Windows perspective. An explanation of the Windows CCI subcommands (the -x options) can be found in the latest CCI user guide.
Windows retains information in its filesystem buffers from previous mountings of volumes. Therefore, it will appear that updates to S-VOLS aren't reflected in the actual device.
This is a problem with the MS Windows filesystem buffer. The fix is the following:
On the S-VOL side
for each mounted S-VOL
- raidscan -x sync <drive-letter>
- raidscan -x umount <drive-letter>
On the P-VOL side
- pairresync -g <group-name>
- raidscan -x sync <drive-letter>
- pairsplit -g <group-name>
On the S-VOL side
- raidscan -x mount <drive-letter>: <harddisk-number>
Note
- raidscan -x drivescan harddisk0,n
will give you the harddisk numbers for all the LDEVs visible to the host.How to mount S-VOLs on Windows Servers