Solved!
Go to SolutionSCV3020 and VMware ESXi 5.5
I hope that you are well!
Hello all -we are experiencing some issues with our new SAN.
- Volume created on SAN vs. VMWAre it looks that VMWare does not see ALL of the spaces that we provision for the volume
On the server DSM:
As you can see we have created one volume of 9TB on the SCV3020 (I have to say that we start with a 3TB on the SAN) so we start to LiveMigrate our VMs from old SAN to this one but in the process we were missing some space so we expand the volume to 9TB but....
Now this is what we see on our ESXI environment:
and this
I did a rescan of Storage, VMFS and so on but it still show 3TB I even expand the volume on the SCV3020 to 12TB but same issue.
Does anyone ever experiencing that kind of issue?
I'm sure that I am missing something...but I can't figure it out!
Your suggestions are more than welcome
Best regards and be safe!
1096
0
Posted April 21st, 2020 05:00
Thank you very much Joerg for your input...
We will then upgrade our ESXI, which was already plan...but not done yet!
Best regards,
1074
0
Posted April 21st, 2020 22:00
I assume that you have some capacity left on the SCv because SCOS creates all volumes as thinprovisioning you should just create another Volume and mount it on the ESX as a Datastore.
If needed you can svMotion your VMs to it and than delete your first Datatore.
I highly suggest to have multiple volumes instead of only one large and single one.
Regards,
Joerg
1058
0
Posted April 23rd, 2020 05:00
Good morning Joerg,
First thank you for your time replying this email it's really appreciated...
That said...we had this discussion (having one BIG Datastore vs. multiple ones) with the Infrastructure Delivery Service guy from Dell when he came on-site to do the installation of our ScV3020. Unfortunately, he did not give a precise answer...his answer was like some people out there like to work with one BIG Datastore and others don't.
Can you quickly answer...why you prefer to work with multiple Datastores instead of one...!!
Best regards Joerg and be safe!
1031
0
Posted April 24th, 2020 11:00
Thats quite simple....
- Dont put all eggs into one basket. A have seen VMFS datacorruoption or LUN trouble
- A SCOS Volume is owned by ONE controller. This one do all the work. If you have only one volume in your SC you only use one controller.... and the other one is idled around and you only get 50% of performance
- If you wanna use vSphere FT 2.0 you need to specify a location for the data copy because with 2.0 all vDisks gets a copy (with 1.0 is was only single vDisk). Placing both copies into the same Datastore make no to much sence(see point 1+2)
- May be you wanna separate a volume to use compression/dedup or syncronisation
- May be you have a need for a different storage profile for some VMs so you needed different Datastore/Volumes
Regards,
Joerg
Origin3k
6 Operator
•
2421 Posts
•
12396 Points
1101
0
Posted April 20th, 2020 21:00
I am surprised that SCv3020 with a modern SCOS is supportet on old vSphere like 5.5. The 5.5 goes out of service a year ago. VMware drops support for 6.0 a month ago.
You havent applied any kind of patches in the last 831 days.
Yes i have seen this kind of problem before that vSphere was unable to expand a Datastore when passing the 2TB. Its a general problem and have nothing to do with SCOS.
See https://kb.vmware.com/s/article/56524 and other.
As a general rule of thumb i do storage related configuration on vCenter Host level rather than vCenter Datastore level.
Regards,
Joerg