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?
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?
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.
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.
SeeingEyeIT
10 Posts
0
December 20th, 2017 13:00
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
10 Posts
0
December 21st, 2017 12:00
Cluster volume that is shared by each host.
SeeingEyeIT
10 Posts
0
December 21st, 2017 12:00
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
10 Posts
0
December 21st, 2017 13:00
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
10 Posts
0
December 21st, 2017 14:00
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.
1 Attachment
Screenshot - 12_21_2017 , 5_26_54 PM.jpg
SeeingEyeIT
10 Posts
0
December 26th, 2017 15:00
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.