vserver nfs pnfs devices create

Create a new pNFS device and its mapping

Availability: This command is available to cluster and Vserver administrators at the advanced privilege level.

Description

The vserver nfs pnfs devices create command creates a pNFS device for a given instance of a volume. The actual creation of pNFS devices is automatically done by the pNFS implementation in Data ONTAP kernel. The usage of this command might interfere with the functionality of the pNFS server. Thus, it is advised that this command not be used without supervision by technical support.

Parameters

[-global-device-table-id <integer>] - Global Device Mapping Table ID
This optional parameter specifies the unique identifier that the pNFS devices subsystem assigns to the device that corresponds to the MSID described below. The pNFS devices implementations keeps track of the global unique identifier that needs to be assigned to this device. It is expected that users need not specifically input the device identifier while creation.
-vserver <vserver name> - Vserver Name
This parameter specifies the Vserver to which the volumes belong.
-msid <integer> - Volume MSID
This parameter uniquely identifies the volume for which you are creating a pNFS device.
-striping-epoch <integer> - Striping Epoch
This optional parameter specifies the striping epoch identifier for a volume for which you are creating a pNFS device. For flexible volumes, the value is always 1.
-device-access <integer> - Device Access Flags
This optional parameter specifies the type of access that is given to the pNFS device that you are creating. If the value is 1, it means write access. If the value if 0, it means read access. By default, the device is created with write access.
-version <integer> - Device Version
This optional parameter specifies the version associated with the pNFS device identifier. By default, the version is set to 1.
[-generation-count <integer>] - Device Generation
This optional parameter specifies the generation count associated with the pNFS device identifier. If a device already exists, the existing device is invalidated and the generation number for the device is bumped. If a device does not already exist, a new device is created with generation number 1.
[-create-time <MM/DD/YYYY HH:MM:SS>] - Device Creation Time
This optional parameter specifies the time at which the device is created. If the parameter is not specified, the time at which the device is created is stored along with the device.
[-mapping-status {available|notavailable}] - Device Mapping Status
This optional parameter specifies if the mapping exists for a device. If the value is set to "available", the mappings will be created in the device mappings table. If the value is set to "notavailable", the mappings will not be created in the device mappings table.

Examples