Friday, October 14, 2011

CTX128272 - Autosize Settings on FlexVols - created on NetApp Filers Might Require Modification - Citrix Knowledge Center

CTX128272 - Autosize Settings on FlexVols - created on NetApp Filers Might Require Modification - Citrix Knowledge Center:

Autosize Settings on FlexVols - created on NetApp Filers Might Require Modification

Document ID: CTX128272 / Created On: Oct 13, 2011 / Updated On: Oct 13, 2011
Average Rating: not yet rated

Symptoms

The following error might appear when you start a Virtual machine:

“Unable to grow volume '' to recover space: Volume cannot be grown beyond maximum growth limit”

This message implies that the autosize option is enabled on the NetApp Filer and the limit for volume growth is set to the default value or too low a value for the volume usage.

Background

The Best Practices guide for using Citrix XenServer 5.x with NetApp Filers recommends using the Autosize option to facilitate Thin Provisioning for the volumes on the storage array. This option might need configuring from the default of 58MB if it is in use.

Resolution

To resolve the preceding issue, Autosize Settings on FlexVols, which is created on NetApp Filers, might need some modification.

To check and resize the Autosize value, complete the following procedure:

  1. To check the current Autosize settings, run the following command on the NetApp Filer:
    vol autosize

    Following is the format of the output of the preceding command:
    “Volume autosize is currently ON for volume '<volume name>'.
    The volume is set to grow to a maximum of , in increments of .”
    Note
    : If the maximum value displayed is 58980 KB with increments set to 80 MB then obviously the volume will not be able to grow at all and the virtual machine will be unusable.
    Therefore, set a more reasonable limit on the volume growth and the increment size as well.
  2. To resize the autosize value, run the following command:
    vol autosize [-m [k|m|g|t]] [-i [k|m|g|t]] [ on | off | reset ]

This document applies to:

No comments:

Post a Comment