Advertisements

EqualLogic: The reported size of the volumes currently belonging to pool default exceeds the pool capacity. OR The maximum in-use space limit for the volumes currently belonging to pool default exceeds the pool capacity.

Posted on December 8, 2009 by mellerbeck

From Tech Support.

You are using thin provisioned volumes and what this message is saying is that if you filled all of your thin provisioned volumes

there would not be enough space in the default pool to make up for it. This message is generated any time a new volume is created, the array restarts or when certain

processes on the array restart. In this case there was a process on the array that restarted itself causing this message to be generated. Our engineering team has been notified of that and will

investigate. In any event no action is required on your part and the message is nothing to be concerned with at this time.

Advertisements

Filed under: equallogic | Leave a comment »

So you bought an equallogic san, now what…. part three

Posted on December 8, 2009 by mellerbeck

This post is more of a compilation of random things I ran across with equallogic and vsphere.

From this post http://communities.vmware.com/message/1272834#1272834

If you present multiple snapshots to vsphere it will not be able to resignature

FYI, this is a bug in vSphere.

If you present multiple snapshots/smart clones of a parent to vSphere it fails to resignature the snapshot volumes. If you only present s a single snapshot of the parent to vSphere at a time it will be able to resignature the snapshot. It works in ESX 3.5 U4 because the resignature process is handled completly differently. We are working with VMware support to aquire a fix to the vSphere resignaturing process.

This fails: (presenting multiple snapshots)

I ran into this bug and it was annoying.

After I upgraded to virtual hardware version 7 I ran into this bug

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011294

Unable to migrate from <source server> to <destination server>: The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level.

The fix

To ensure that VMotion is successful:
  1. Power down the virtual machine.
  2. Click the link to Edit Settings of the virtual machine.
  3. Click the Options tab.
  4. Select CPUID Mask under Advanced.
  5. Click Advanced.
  6. Click Reset All to Default.
  7. Click OK.
  8. Click OK again.
  9. Power on the virtual machine and migrate.

This tip also might be useful if you are adding a lot of Volumes

http://www.yellow-bricks.com/2009/08/04/automatic-rescan-of-your-hbas/

It can temporarily turn of the rescan of your hba’s to stop a rescan storm.

This next link has a lot more info on using IOmeter

http://vinf.net/2009/11/19/comparing-the-io-performance-of-2-or-more-virtual-machines-ssd-sata-iometer/

Another common thing that might happen to you when you upgrade the virtual hardware is this message: the ip address you have entered is already assigned

The steps to take care of that are linked below.

https://michaelellerbeck.com/2009/06/15/the-ip-address-you-have-entered-is-already-assigned/

I ran across this VMware document which has some useful info. http://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdf

What did I glean, “Make sure the NICs are configured to use autonegotiation to set speed and duplex settings, and are
configured for full-duplex mode.”

Also, I learned about the existence of the vmware paravirtual scsi controller type (but I have no clue what to do with it)

Filed under: Uncategorized | 1 Comment »