NetApp Manage ONTAP

APIs in Category: file | Cluster-Mode API version 1.21

file-assign-qos | The path and filename values used in these APIs are "NFS" filenames by default. If a file is created with a name that is illegal in CIFS, CIFS access to the file will need to use the file's 8.3 name. Similarly, if two filenames created by these APIs differ only by case (e.g. "a" and "A"), CIFS access will see the 8.3 name for the second one created. To access files or directories with Unicode file names, the UTF-8 equivalent of the Unicode path can be used. If a file contains Unicode-format data, the filer returns all the data in the file including the identifier in the first two bytes of the file which indicates the file contains Unicode data (0xFEFF). A file may optionally contain multiple distinct streams of data. A stream is an on disk structure containing a sequence of bytes, analogous to a file. A stream associated with a file is identified by a name, and data may be read or written to a file or stream. A stream can be thought of as a hidden file associated with a base file, and is visible in the name space of the base file. Streams are typically used to store metadata associated with the base file

file-assign-qos | [top]

> Manage the association of QoS policy group to a specified file. QoS Policy groups define measurable Service Level Objectives (SLOs) that apply to the storage object with which the policy group is associated. In Data ONTAP 8.2 hierarchical QoS is not supported i.e. QoS policy groups cannot be assigned to multiple objects in the file's storage hierarchy - such as the parent LUN, volume or Vserver.

> Input Name | Range | Type | Description
> file |  | string | Complete file path of the file without a trailing slash.
> qos-policy-group-name |  | string | The QoS Policy Group Name that is to be associated with this file in order to enforce Service Level Objectives (SLO). NOTE: none is a reserved keyword for deleting the association of the file with a QoS policy group.
> volume |  | volume-name | Name of the Volume in which the file resides.
> vserver |  | vserver-name | Name of the Vserver in which the volume that hosts the file resides.

> Errno | Description
> E_QOS_OBJECT_OVERLAP_ERROR |  |
> E_QOS_NO_SUCH_PG |  |
> E_QOS_TOO_MANY_USER_WIDS |  |
> E_QOS_GENERAP_OP_ERROR |  |
> E_QOS_VSERVERIZATION_VIOLATION |  |
> E_QOS_FILE_IS_LUN |  |
> E_QOS_FILE_ACCESS_ERROR |  |

Element definition: volume-name | [top]

> The name of the volume. Volume names can contain letters, numbers, and the underscore character (_). The first character must be a letter or an underscore. When creating a Cluster-Mode volume, the user can specify at most 203 characters. If the prefix '/vol/' appears in the volume name, it is striped out and the characters that follow the prefix constitute the actual volume name. Volume names are scoped by their owning Vserver in a cluster, with each Vserver's volume namespace being totally independent. Thus, any Vserver 'S' in a cluster cannot have two volumes with the same name 'V'. However, two different Vservers in the same cluster can each have a volume named 'V'. For example, any given Vserver in a cluster can only have at most one volume named 'vol0'. However, two different Vservers S1 and S2 in the cluster may each have a volume named 'vol0'.

> [none]

Element definition: vserver-name | [top]

> The name of the Vserver.

> [none]