volume file modify

Manage the association of a QoS policy group with a file

Availability: This command is available to cluster administrators at the admin privilege level.

Description

This command adds and removes files from QoS policy groups. QoS policy groups define measurable service level objectives (SLOs) that apply to the storage objects with which the policy group is associated. A QoS policy group associated with this file can be created, modified, and deleted. You cannot associate a file to a QoS policy group if a LUN was created from the file.

This command is not supported on FlexGroups or Infinite Volumes.

Parameters

-vserver <vserver name> - Vserver Managing Volume
This specifies the Vserver on which the volume (containing the file) resides.
-volume <volume name> - Volume Name
This specifies the name of the volume. The name must be unique within the hosting Vserver.
-file <text> - File Path
This specifies the actual path of the file with respect to the volume.
{ [-qos-policy-group <text>] - QoS Policy Group Name
This option associates the file with a QoS policy group. This policy group manages storage system resources to deliver your desired level of service. If you do not assign a policy to a file, the system will not monitor and control the traffic to it. To remove this file from a QoS policy group, enter the reserved keyword “none”.
| [-qos-adaptive-policy-group <text>]} - QoS Adaptive Policy Group Name
This optional parameter specifies which QoS adaptive policy group to apply to the file. This policy group defines measurable service level objectives (SLOs) and Service Level Agreements (SLAs) that adjust based on the file's allocated space or used space. To remove this file from an adaptive policy group, enter the reserved keyword "none".
[-caching-policy <text>] - Caching Policy Name
This optionally specifies the caching policy to apply to the file. A caching policy defines how the system caches this volume's data in Flash Cache modules. If a caching policy is not assigned to this file, the system uses the caching policy that is assigned to the containing volume. If a caching policy is not assigned to the containing volume, the system uses the caching policy that is assigned to the containing Vserver. If a caching policy is not assigned to the containing Vserver, the system uses the default cluster-wide policy. The available caching policies are:
  • none - Does not cache any user data or metadata blocks.
  • auto - Read caches all metadata and randomly read user data blocks, and write caches all randomly overwritten user data blocks.
  • meta - Read caches only metadata blocks.
  • random_read - Read caches all metadata and randomly read user data blocks.
  • random_read_write - Read caches all metadata, randomly read and randomly written user data blocks.
  • all_read - Read caches all metadata, randomly read and sequentially read user data blocks.
  • all_read_random_write - Read caches all metadata, randomly read, sequentially read, and randomly written user data.
  • all - Read caches all data blocks read and written. It does not do any write caching.
Default caching-policy is auto.

Examples

    cluster1::> vol file modify -vserver vs0 -volume vs0_vol56 -file 1.txt -qos-policy-group fast -cache all-read