container set label :
Dell
Command Line Interface
Reference
Back to Contents Page
container set label
To assign a new label to the specified container or to assign a label to a container that has no label, use the container set label command.
The following commands have a /label switch that allows you to assign a label to the container when you create it:
-
container create mstripe (a multilevel stripe set)
-
container create mvolume (a multilevel volume set)
-
container create raid5 (a RAID-5 set)
-
container create stripe (a stripe set)
-
container create volume (a volume set)
The label you specify with the container set label command and the /label switch associated with the previously listed container create commands is not the label that displays in Windows Explorer. The label displayed by Windows Explorer comes from the label specified with the container format command.
Command Availability
This command is supported on the following operating systems:
Syntax
container set label {container} {string}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to which you want to assign a label.
{string}
Specifies the label you want to assign to the container. The label is a string of up to sixteen characters.
Examples
Before assigning a label to a specific container, use the container list command to obtain information about any existing containers. As the following example shows, there is a container 0 (a volume set) on this controller with no label assigned to it (as evidenced by no label in the Num Label column):
AFA0> container list
Executing: container list
Num Total Oth Chunk Scsi Partition
Dr Label Type Size Ctr Size Usage B:ID:L Offset:Size
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Volume 15.0MB None 0:02:0 64.0KB: 15.0MB
The following example assigns the label Tigris to container 0:
AFA0> container set label 0 Tigris
Executing: container set label 0 "Tigris"
Use the container list command after using the container set label command to display the new label, as in the following example:
AFA0> container list
Executing: container list
Num Total Oth Chunk Scsi Partition
Dr Label Type Size Ctr Size Usage B:ID:L Offset:Size
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Volume 15.0MB None 0:02:0 64.0KB: 15.0MB
Tigris
As the example shows, the new label Tigris now appears in the Num Label column.
Related Information
container Commands:
container show cache
To display the current cache parameters associated with a specific container, use the container show cache command. Typically, you use this command after setting cache parameters for a specific container using the container set cache command.
Command Availability
This command is supported on the following operating systems:
Syntax
container show cache {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container whose associated cache parameters you want to display.
Examples
Before setting cache parameters for a specific container, use the container list command to obtain information about any existing containers. As the following example shows, there is a container 0 (a volume set) on this controller with no file system on it (as evidenced by None displayed in the Usage column). Assume the cache parameters for this container were previously set with the container set cache command:
AFA0> container list
Executing: container list
Num Total Oth Chunk Scsi Partition
Dr Label Type Size Ctr Size Usage B:ID:L Offset:Size
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Volume 15.0MB None 0:02:0 64.0KB: 15.0MB
The following example displays the cache parameters for container 0:
AFA0> container show cache 0
Executing: container show cache 0
Global Container Read Cache Size : 5345280
Global Container Write Cache Size : 1970176
Read Cache Setting : ENABLED
Write Cache Setting : ENABLED
Write Cache Status : ENABLED
The following list provides a brief description of the items that appear as a result of using the container show cache command:
- Global Container Read Cache Size
- This item indicates the number of blocks devoted to the read cache.
- Global Container Write Cache Size
- This item indicates the number of blocks devoted to the write cache.
- Read Cache Setting
- This item indicates whether the read cache is set for the container. The value
ENABLED indicates the read cache is set for this container. The value DISABLED indicates the read cache is disabled for this container.
- Write Cache Setting
- This item indicates whether the write cache is set for the container. This item can display one of the following values:
-
| Value |
Meaning |
DISABLE |
The write cache is disabled for this container |
ENABLE ALWAYS |
The write cache setting for the specified container is enabled always. This means the controller forces the enabling of the container's write cache even if write data could be lost due to no battery or a bad battery. |
ENABLE WHEN PROTECTED |
The write cache setting for the specified container is enabled when protected. This means the controller enables the container's write cache only if a battery is present and its status is OK. |
- Write Cache Status
- This item indicates the current status of the write cache for the container and, where appropriate, the status of the battery. This item can display one of the following values:
-
| Value |
Meaning |
Active, not protected |
The status of the write cache for this container is as follows:
n Active -- The write cache can accept write operations from the container.
n Not protected -- The write cache is force-enabled. Thus, the write cache accepts write operations even if write data could be lost due to no battery present or a bad battery on the controller.
n This status also indicates that the battery status is OK.
|
Active, not protected, battery low |
The status of the write cache for this container is as follows:
n Active -- The write cache can accept write operations from the container.
n Not protected -- The write cache is force-enabled. Thus, the write cache accepts write operations even if write data could be lost due to no battery present or a bad battery on the controller.
n This status also indicates that the battery status is low.
|
Active, not protected, battery not present |
The status of the write cache for this container is as follows:
n Active -- The write cache can accept write operations from the container.
n Not protected -- The write cache is force-enabled. Thus, the write cache accepts write operations even if write data could be lost due to no battery present or a bad battery on the controller.
n This status also indicates that the battery is not present on the controller.
|
Active, not protected, battery reconditioning |
The status of the write cache for this container is as follows:
n Active -- The write cache can accept write operations from the container.
n Not protected -- The write cache is force-enabled. Thus, the write cache accepts write operations even if write data could be lost due to no battery present or a bad battery on the controller.
n This status also indicates that the battery is being reconditioned.
|
Active, protected |
The status of the write cache for this container is as follows:
n Active -- The write cache can accept write operations from the container.
n Protected -- The write cache is enabled only if a battery is present and its status is OK.
n This status also indicates that the controller's battery is present and its status is OK.
|
Inactive, battery low |
The status of the write cache for this container is as follows:
n Inactive -- The write cache cannot accept write operations from the container.
n Battery low -- This controller's battery power is low.
|
Inactive, battery not present |
The status of the write cache for this container is as follows:
n Inactive -- The write cache cannot accept write operations from the container.
n Battery not present -- This controller has no battery.
|
Inactive, battery reconditioning |
The status of the write cache for this container is as follows:
n Inactive -- The write cache cannot accept write operations from the container.
n Battery low -- The controller's battery is being reconditioned.
|
Inactive, cache disabled |
The status of the write cache for this container is as follows:
n Inactive -- The write cache cannot accept write operations from the container.
n Cache disabled -- The user disabled the write cache by using the container set cache command and setting the appropriate switches.
|
Inactive, write not supported |
The status of the write cache for this container is as follows:
n Inactive -- The write cache cannot accept write operations from the container.
n Battery not supported -- This controller does not support a battery.
|
Related Information
container Commands:
container show failover
To display a list of failover disks assigned to a container, use the container show failover command. You assign failover disks to a container with the container set failover command.
Command Availability
This command is supported on the following operating systems:
Syntax
container show failover [{container}]
Parameters
{container}
Specifies the ID number (0 to 63) of the container whose assigned failover disk(s) you want to display. If you do not specify this parameter, the command displays all containers and their assigned failover disk(s).
Examples
The following example shows the failover disks assigned to container 0:
AFA0> container show failover 0
Executing: container show failover 0
Container Scsi B:ID:L
--------- ----------------------------------
0 0:03:0 0:04:0
The example shows that container 0 was assigned disks 0:03:0 and 0:04:0 as failover disks.
Related Information
container Commands:
container split
To split a mirror set or a multilevel container of mirror sets into two separate single-partition volume sets or two multilevel containers of single-partition volume sets, use the container split command. Once this command completes execution, the two volume sets cannot be merged.
Before using this command to split a container, shut down system applications (such as, databases) in order to flush application data to the controller.
When you split a mirror set or a multilevel container of mirror sets, the system creates a new (referred to as the split) container. The split container contains half of the storage data from the original (referred to as the master) container (mirror set). In addition, the split container has an identical copy of the data from the old disk at the time of the split operation.
On Windows NT, the split container's file system may be inconsistent and you should verify and repair it as follows:
- Assign a drive letter to the split container using the
container assign drive_letter command.
- Run the Windows NT
CHKDSK command with the /F switch. See your Windows documentation for information on how to use the CHKDSK command.
Command Availability
This command is supported on the following operating systems:
Syntax
container split {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container (mirror set or multilevel container of mirror sets) to split into two separate containers.
Examples
Before splitting a mirror set or a multilevel container of mirror sets, use the container list command to obtain information about any existing containers. As the following example shows, there is one existing container (container 0, a mirror set) on this controller at the time the mirror set is split:
AFA0> container list
Executing: container list
Num Total Oth Chunk Scsi Partition
Dr Label Type Size Ctr Size Usage B:ID:L Offset:Size
-- ----- ------ ------ --- ------ ------- ------ -------------
F: 0 Mirror 10.0MB NTFS 0:02:0 64.0KB: 10.0MB
0:02:0 10.0MB: 10.0MB
The following example shows how to split a mirror set:
AFA0> container split 0
Executing: container split 0
Container 1 created
On UNIX systems, the message displayed after you execute the container split command includes the special file associated with the newly created split container.
Use the container list command after using the container split command to display information about the split mirror set, as in the following example:
AFA0> container list
Executing: container list
Num Total Oth Chunk Scsi Partition
Dr Label Type Size Ctr Size Usage B:ID:L Offset:Size
-- ----- ------ ------ --- ------ ------- ------ -------------
F: 0 Volume 10.0MB NTFS 0:02:0 64.0KB: 10.0MB
1 Volume 10.0MB NTFS 0:02:0 10.0MB: 10.0MB
The following list describes the change to the display as the result of splitting a mirror set with the container split command:
- The Num Label column displays the IDs (in the example, 0 and 1) of the split mirror set. Container 0 is the master container; container 1 is the split container.
- This column also displays the label(s) assigned to the container(s) when the container(s) was created. If no label(s) was assigned to the container(s) then no label(s) appears in the column.
- On UNIX systems, the special file associated with the container also appears in this column.
- The Type column displays Volume as the container type for a split mirror set.
- The Usage column displays NTFS to indicate that file systems exist on both containers. You can create an NTFS or FAT file system on a container by using the
container format command.
- The Scsi B:ID:L column displays the SCSI device IDs for the disk on which the split mirror set (now two volume sets) reside. In the example, the SCSI device ID is 0:02:0.
- The Partition Offset:Size column displays the partition offsets and sizes for the partition associated with the split mirror set (now two volume sets).
- If a partition is dead, the ":" (colon) in the Partition Offset:Size column changes to a "!" (exclamation point). See the
disk remove dead_partitions (disk remove dead_partitions) command for more information on dead partitions.
Related Information
container Commands:
disk Commands:
container unlock
Caution:
Use the container unlock command only
under the direction of Technical Support.
To unlock a container so it can be moved, deleted, made read-only, and used to create a multilevel container, use the container unlock command.
Command Availability
This command is supported on the following operating systems:
Syntax
container unlock {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to unlock.
Examples
Before unlocking a container, use the container list command (with the /full switch) to obtain information about any existing containers. As the following example shows, there is a container 0 (a volume set) on this controller. Note that the Lk column displays an L, which indicates that container 0 was previously locked with the container lock command:
AFA0> container list /full
Executing: container list /full=TRUE
Num Total Oth Chunk Scsi
Dr Label Type Size Ctr Size Usage B:ID:L Lk
-- ----- ------ ------ --- ------ ------- -------- --
F: 0 Volume 10.0MB NTFS 0:02:0 L
Note that the example eliminates some items in the container list display so that you can see an example of the Lk column.
The following example shows how to unlock container 0:
AFA0> container unlock 0
Executing: container unlock 0
Use the container list command (with the /full switch) after using the container unlock command to display information about the unlocked container, as in the following example:
AFA0> container list /full
Executing: container list /full=TRUE
Num Total Oth Chunk Scsi
Dr Label Type Size Ctr Size Usage B:ID:L Lk
-- ----- ------ ------ --- ------ ------- -------- --
F: 0 Volume 10.0MB NTFS 0:02:0
Note that the example eliminates some items in the container list display so that you can see an example of the Lk column.
The following list describes the change to the display as the result of unlocking a container (in this example, container 0) with the container unlock command:
- The Lk column displays a blank (instead of an L)
to indicate that the specified container is now unlocked.
Related Information
container Commands:
container unmirror
To unmirror a mirror set, resulting in a single-partition volume set and freespace, use the container unmirror command. Note that there is no equivalent command for a multilevel container of mirror sets. To unmirror a multilevel container of mirror sets, use this command for each underlying mirror set.
Command Availability
This command is supported on the following operating systems:
Syntax
container unmirror {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the mirror set to unmirror. You previously created the mirror set by using the container create mirror or container create mmirror command.
Examples
Before unmirroring a mirror set, use the container list command to obtain information about any existing containers. As the following example shows, there is one existing container (container 0, a mirror set) on this controller at the time the mirror set is unmirrored:
AFA0> container list
Executing: container list
Num Total Oth Chunk Scsi
Dr Label Type Size Ctr Size Usage B:ID:L State
-- ----- ------ ------ --- ------ ------- -------- -----
0 Mirror 10.0MB NTFS 0:02:0 Normal
0:03:0
Note that the example eliminates some items in the container list display so that you can see an example of the State column.
The following example shows how to unmirror a mirror set from the mirror set that resides on SCSI device (0,3,0):
AFA0> container unmirror 0
Executing: container unmirror 0
Use the container list command after using the container create unmirror command to display information about the unmirrored container, as in the following example:
AFA0> container list
Executing: container list
Num Total Oth Chunk Scsi
Dr Label Type Size Ctr Size Usage B:ID:L State
-- ----- ------ ------ --- ------ ------- -------- -----
D: 0 Volume 10.0MB NTFS 0:02:0
Note that the example eliminates some items in the container list display so that you can see an example of the State column.
The following list describes the changes to the display as a result of using the container unmirror command:
- The Type column displays Volume, which indicates that the mirror set was created from a Volume set.
- The State column displays a blank space instead of Normal. The Normal state is displayed only for mirror sets.
- The Scsi B:ID:L column displays only one SCSI ID.
- The Partition Offset:Size column displays only one partition offset and size.
- If a partition is dead, the ":" (colon) in the Partition Offset:Size column changes to a "!" (exclamation point). See the
disk remove dead_partitions (disk remove dead_partitions) command for more information on dead partitions.
Related Information
container Commands:
disk Commands:
Back to Contents Page
| 
