Shrinking Space, Creating Volumes & Disk Management Problems

Question

I have created two new volumes in preparation for configuring SQL Failovers. To do this, I needed to free up some space. Accordingly, I set a volume off-line, SSH'ed to the SAN Group and shrank the volume via the CLI. Put the volume back on line. Now I had more space.

I created the volumes and connected the iSCSI initiators. Worked OK on Host #1.

Here are my problems:

1) The volume that I shrank still shows up in Disk Management in its original size. Moreover, the Volume Label is different than the Volume name. How do I correct these?

2) I can see the two new volumes on Host #1 but on Hosts #2 and #3 they show up as Inactive in the iSCSI initiator. When I try to connect them, I get a :Authorization Failure" message.

Pointers to documentation or Videos welcome.

Thanks.

SeeingEyeIT · Answer

Don- Thank you.  You are correct on both counts.  I've fixed the second item.  Can you give me some ideas on how to fix the first item? Steve

SeeingEyeIT · Answer

Cluster volume that is shared by each host.

SeeingEyeIT · Answer

Hi Don -

I have successfully resized the partition on one of my three hosts. I restored my VMs from a snapshot and 4 out of 5 are successfully running. However, the other two hosts still show the old disk at the expanded size. Do I have to resize it separately on each host?

Steve

SeeingEyeIT · Answer

This is weird.  I resized the volume on host #1 from 6 TB to 3 TB and renamed it.  Hosts #2 and #3 show the old size (6 TB) and the old name.  I rebooted all three hosts.  I start the ASM on one of the hosts and was preparing to take screenshots to show you the difference.  All of the sudden, host #1 has reverted back to the old size and name!  How can this be?

SeeingEyeIT · Answer

Here is a screenshot from Failover Cluster Manager.  As you can see, the top line shows the volume TSEV-Data as 2.93 TB.  But the bottom panel shows the same volume as 5.88 TB free out of 6.0 TB.

SeeingEyeIT · Answer

Don - I'm still struggling with this. The array side is 3 TB, which is good. The CSV side shows 6 TB. If I shrink the CSV side, I lose the VMs and I have to restore from the array side, which then resets the CSV back to 6 TB instead of 3 TB. It's an endless loop.

I also seem unable to back up the VMs to another location because of VSS problems. It would seem that all of these things are interrelated? I would really appreciate your thoughts on how to proceed.

EqualLogic

Shrinking Space, Creating Volumes & Disk Management Problems

Was this post helpful?