Assign ownership of a disk to a system
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The storage disk assign command is used to assign ownership
of an unowned disk or array LUN to a specific node. You can also use this command to change
the ownership of a disk or an array LUN to another node. You can designate disk ownership
by specifying disk names, array LUN names, wildcards, or all (for all disks or array LUNs
visible to the node). For disks, you can also set up disk ownership autoassignment.
You can also assign disks to a particular pool. You can also assign disks by
copying ownership from another disk.
Parameters
- { [-disk <disk path name>] - Disk Path
- This specifies the disk or array LUN that is to be assigned. Disk names take one of the following forms:
- Disks are named in the form
<stack-id>.<shelf>.<bay>
- Disks on multi-disk carriers are named in the form
<stack-id>.<shelf>.<bay>.<lun>
- Virtual disks are named in the form <prefix>.<number>,
where prefix is the storage array's prefix and number is a unique
ascending number.
Disk names take one of the following forms on clusters that are not yet
fully upgraded to Data ONTAP 8.3: - Disks that are not attached to a switch are named in the form
<node>:<host_adapter>.<loop_ID>.
For disks with a LUN, the form is
<node>:<host_adapter>.<loop_ID>L<LUN>.
For instance, disk number 16 on host adapter 1a on a node named node0a
is named node0a:1a.16.
The same disk on LUN lun0 is named node0a:1a.16Llun0.
- Disks that are attached to a switch are named in the form
<node>:<switch_name>:<switch_port>.<loop_ID>.
For disks with a LUN, the form is
<node>:<switch_name>:<switch_port>.<loop_ID>L<LUN>.
For instance, disk number 08 on port 11 of switch fc1 on a node named
node0a is named node0a:fc1:11.08.
The same disk on LUN lun1 is named node0a:fc1:11.08Llun1.
Before the cluster is upgraded to Data ONTAP 8.3, the same disk can
have multiple disk names, depending on how the disk is connected. For
example, a disk known to a node named alpha as alpha:1a.19 can be known
to a node named beta as beta:0b.37. All names are listed in the output
of queries and are equally valid. To determine a disk's unique identity,
run a detailed query and look for the disk's universal unique identifier
(UUID) or serial number.
A subset of disks or array LUNs can be assigned using the wildcard character (*)
in the -disk parameter.
Either the -owner, the
-sysid, or the -copy-ownership-from parameter must be specified with the
-disk parameter. Do not use the
-node parameter with the
-disk parameter.
- | -disklist <disk path name>, ... - Disk list
-
This specifies the List of disks to be assigned.
- | -all [true] - Assign All Disks
- This optional parameter causes assignment of all visible unowned
disks or array LUNs to the node specified in the -node
parameter. The -node parameter must be specified with
the -all parameter. When the
-copy-ownership-from parameter is specified with
the -node parameter, it assigns disk ownership based on
the -copy-ownership-from parameter; otherwise it assigns
ownership of the disks based on the -node parameter.
Do not use the -owner or the
-sysid parameter with the
-all parameter.
- | [-type | -T {ATA | BSAS | FCAL | FSAS | LUN | MSATA | SAS | SSD | VMDISK | SSD-NVM}] - Storage Type
- This optional parameter assigns ownership of a specific type of disk
or array LUN (or a set of disks/array LUNs) to a node.
The -count parameter must be specified with the
-type parameter.
- -count | -n <integer> - Disk Count
- This optional parameter assigns ownership of a number
of disks or array LUNs specified in the -count
parameter, to a node.
- | -auto [true]} - Auto Assign
- This optional parameter causes all visible disks eligible for
autoassignment to be immediately assigned to the node specified
in the -node parameter, regardless of
the setting of the disk.auto_assign option. Only unowned disks on
loops or stacks owned wholly by that system and which have the same
pool information will be assigned.
The -node parameter must be specified with the
-auto parameter.
Do not use the -owner, the
-sysid, or
the -copy-ownership-from parameter with the
-auto parameter.
When possible, use the -auto
parameter rather than the -all parameter to conform to
disk ownership best practices. The -auto
parameter is ignored for array LUNs.
- [-pool | -p <integer>] - Pool
- This optional parameter specifies the pool to which a
disk must be assigned. It can take values of Pool0 or Pool1.
- { [-owner | -o <nodename>] - Owner Name
- This optional parameter specifies the node to which the
disk or array LUN has to be assigned.
- [-sysid | -s <nvramid>] - New Owner ID
- This optional parameter specifies the serial number
(NVRAM ID) of the node to which the disk or array LUN has to be assigned.
- | [-copy-ownership-from <disk path name>]} - Disk Name to Copy Ownership
-
This optional parameter specifies the disk name from where the node needs to
copy disk ownership information. You can use this parameter for
disks to have the same ownership as the provided input disk.
- [-checksum | -c {block|zoned|advanced_zoned}] - Checksum Compatibility
- This optional parameter is used to set the
checksum type for a disk or an array LUN. The possible values are
block, zoned, and
advanced_zoned. This operation will fail if the
specified disk is incompatible with the specified checksum type.
A newly created aggregate with zoned checksum array LUNs is assigned
advanced zoned checksum (AZCS) checksum type. AZCS checksum type provides
more functionality than the "version 1" zoned checksum type which
has been supported in previous Data ONTAP releases. Zoned checksum
spare array LUNs added to an existing zoned checksum aggregate
continue to be zoned checksum. Zoned checksum spare array LUNs
added to an AZCS checksum type aggregate use the AZCS checksum scheme
for managing checksums.
For some disks (e.g. FCAL, SSD, SAS disks), the checksum type cannot be
modified. For more information on modifying the checksum type, refer to the
"Physical Storage Management Guide".
- [-force | -f [true]] - Force Flag
- This optional parameter forces the assignment of
ownership of an already owned disk to a node. This parameter could
also be used to assign an array LUN with a redundancy error,
for example, if the array LUN is available on only one path. For a disk
which is part of a live aggregate, even specification of the
-force parameter would not force the
assignment, since it would be catastrophic.
- [-node | -N <nodename>] - Node Name (For Auto Assign)
- This optional parameter is used with either the
-auto or the -all
parameter. If used with the -auto parameter,
all disks which are visible to the node specified in the
-node parameter and which are eligible for
autoassignment would be assigned to it. If used with the
-all parameter, all unowned disks or array
LUNs visible to the node would be assigned to it.
- { [-root [true]] - Root Partition of Root-Data or Root-Data1-Data2 Partitioned Disk (privilege: advanced)
-
This optional parameter assigns the root partition of a
root-data/root-data1-data2 partitioned disk.
You cannot use this parameter with disks that are part of a storage pool.
The default value is false.
- | [-data [true]] - Data Partition of Root-Data Partitioned Disk (privilege: advanced)
-
This optional parameter assigns the data partition of a root-data partitioned disk.
You cannot use this parameter with disks that are part of a storage pool.
The default value is false.
- | [-data1 [true]] - Data1 Partition of Root-Data1-Data2 Partitioned Disk (privilege: advanced)
-
This optional parameter assigns the data1 partition of a root-data1-data2 partitioned disk.
You cannot use this parameter with disks that are part of a storage pool.
The default value is false.
- | [-data2 [true]]} - Data2 Partition of Root-Data1-Data2 Partitioned Disk (privilege: advanced)
-
This optional parameter assigns the data2 partition of a root-data1-data2 partitioned disk.
You cannot use this parameter with disks that are part of a storage pool.
The default value is false.
Examples
The following example assigns ownership of an unowned disk named
1.
1.
16 to a node
named
node1:
cluster1::> storage disk assign -disk 1.1.16 -owner node1
The following example assigns all unowned disks or array LUNs visible to a node named
node1 to itself:
cluster1::> storage disk assign -all -node node1
The following example autoassigns all unowned disks (eligible for autoassignment)
visible to a node named
node1 to itself:
cluster1::> storage disk assign -auto -node node1
The following two examples show the working of the
-force
parameter with a spare disk that is already owned by another system:
cluster1::> storage disk assign -disk 1.1.16 -owner node1
Error: command failed: Failed to assign disks. Reason: Disk 1.1.16 is
already owned.
cluster1::> storage disk assign -disk 1.1.16 -owner node1 -force
Success.
The following example assigns ownership of the set of unowned disks
on
<stack> 1, to a node named
node1:
cluster1::> storage disk assign -disk 1.* -owner node1
The following example assigns ownership of unowned disk
1.
1.
16 by copying ownership
from disk
1.
1.
18:
cluster1::> storage disk assign -disk 1.1.16
-copy-ownership-from 1.1.18
The following example assigns all unowned disks visible to a node named
node1 by copying ownership from disk
1.
1.
18:
cluster1::> storage disk assign -all -node node1
-copy-ownership-from 1.1.18
The following example assigns the root partition of disk
1.
1.
16 to node1.
cluster1::> storage disk assign -disk 1.1.16 -owner node1 -root true
-force true
The following example assigns the data partition of root-data partitioned disk
1.
1.
16 to node1.
cluster1::> storage disk assign -disk 1.1.16 -owner node1 -data true
-force true
The following example assigns the data1 partition of root-data1-data2 partitioned disk
1.
1.
24 to node1.
cluster1::> storage disk assign -disk 1.1.24 -owner node1 -data1 true
-force true
The following example assigns the data2 partition of root-data1-data2 partitioned disk
1.
1.
24 to node1.z33
cluster1::> storage disk assign -disk 1.1.24 -owner node1 -data2 true
-force true