Table 1. container Commands
The container commands are discussed in alphabetical order and use the following syntax:
container action [object] [/switch{=value}]
[parameter]
container add_level
To create a multilevel volume set from an existing container by adding a volume set on top of the container, use the container add_level command. The existing container cannot be a multilevel container.
The container add_level command allows dynamic expansion of a container and can be executed even while a container is in use. After executing the command, you can use the container extend mvolume command to add more space.
Command Availability
This command is supported on the following operating systems:
Syntax
container add_level {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to convert to a multilevel volume set.
The specified container must not be a multilevel container.
Examples
Before creating a multilevel volume set, use the container list command to obtain information about any existing containers.
As the following example shows, there is a container 0 (a stripe set) on this controller:
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 Stripe 45MB 32KB None 0:02:0 64.0KB: 15.0MB
0:03:0 64.0KB: 15.0MB
0:04:0 64.0KB: 15.0MB
The following example creates a multilevel volume set on top of container 0, which is a stripe set previously created with the container create stripe command:
AFA0> container add_level 0
Executing: container add_level 0
Use the container list command after using the container add_level command to display information about the multilevel volume 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
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Volume 45MB None
63 Stripe 45MB 32KB 0:02:0 64.0KB: 15.0MB
0:03:0 64.0KB: 15.0MB
0:04:0 64.0KB: 15.0MB
The following list describes the change to the display as a result of creating a multilevel volume set with the container add_level command:
- The Num Label column displays two ID numbers. The first ID (0) is the newly created volume set. The second ID (63) is the original container (the stripe set).
- If you specified a label when creating the multilevel volume set, it appears in this column. Because no label was specified when the multilevel volume set was created, no label appears in the column.
- The Type column displays two container types: Volume and Stripe. The Volume container type indicates that the newly created container is a volume set. This is the container created after the
container add_level command completes.
- The Stripe container type indicates the container whose ID was specified to the
container add_level command. This is the original container previously created with the container create stripe command.
- Thus, the example shows a multilevel volume set that consists of a stripe set.
Related Information
container Commands:
container assign drive_letter
To assign a drive letter to a container, use the container assign drive_letter command.
Command Availability
This command is supported only on Windows NT.
Syntax
container assign drive_letter {container}[{string}]
Parameters
{container}
Specifies the ID number (0 to 23) of the container on which you want to assign a drive letter.
{string}
Specifies a character that represents a drive letter. Use of the colon (:) after the drive letter is optional. The specified drive letter must not be used by any other device. If you specify a drive letter in use by another device, the command displays an appropriate error message.
If you do not specify the string parameter, the command uses the next available drive letter.
If you previously assigned a drive letter, the command replaces the old letter with the one you specify. You can specify a maximum of twenty-four drive letters. If you exceed the maximum, the command displays an error message indicating that there are no more available drive letters to assign.
Examples
Before assigning a drive letter to a 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:
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 10MB None 0:02:0 64.0KB: 10.0MB
The previous display shows that container 0 has no drive letter assigned to it. The following example assigns drive letter F to container 0:
AFA0> container assign drive_letter 0 F
Executing: container assign drive_letter 0 "F"
Drive Letter F: assigned to Container 0
Use the container list command after using the container assign drive_letter command to display information about the container on which you just assigned a drive letter, as in the following example:
Num Total Oth Chunk Scsi Partition
Dr Label Type Size Ctr Size Usage B:ID:L Offset:Size
-- ----- ------ ------ --- ------ ------- ------ -------------
F: 0 Volume 10MB None 0:02:0 64.0KB: 10.0MB
The following list describes the change to the display as the result of assigning a drive letter on a container (in this example, container 0) with the container assign drive_letter command:
- The Dr column displays the assigned drive letter. The assigned drive letter is the next available drive letter if you did not specify one. In this example, the letter
F appears in the Dr column.
Related Information
container Commands: container list (container list)
container clear
To clear an entire container, use the container clear command. A container that has open files cannot be cleared. A container with a file system can be cleared only if you specify the /always switch.
Command Availability
This command is supported on the following operating systems:
Before clearing a container on a NetWare system, you must first go to the NetWare console and remove the corresponding volume and partition.
For information on how to perform these operations, see the appropriate NetWare documentation. For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User's Guide.
Syntax
container clear [/always{=boolean}]
[/wait{=boolean}] {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to clear.
Switches
/always{=boolean}
Specifies whether to clear the container, even if it has data on it. If you specify TRUE, the command clears the container even if it has data on it.
The default is FALSE (i.e., the command clears the container only if it has no data on it). In both cases, all user files must be closed; the /always switch cannot override this restriction.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/wait{=boolean}
Specifies whether to clear the container synchronously or asynchronously. If you set this switch to TRUE, the command clears the container synchronously and the command prompt does not return until the clear container task completes.
The default is FALSE (i.e., the command clears the container asynchronously and the command prompt returns immediately).
This switch is supported on the following operating systems:
Examples
Before clearing a 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:
Num Total Oth Chunk Scsi Partition
Dr Label Type Size Ctr Size Usage B:ID:L Offset:Size
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Volume 10MB None 0:02:0 64.0KB: 10.0MB
The following example clears a volume set on SCSI disk (0,2,0):
AFA0> container clear 0
Executing: container clear 0
As the command executes, note the title bar of the DOS window displays the status of the command. For example:
Stat:OK!Task:101,Func:CTC Ctr:0,State:RUN 97.0%
See CLI Status Information for detailed information on the status information that the command displays in the title bar as it executes the task.
Use the container list command after using the container clear command to display information about the cleared container, as in the following example:
AFA0> container list
Executing: container list 0
Num Total Oth Chunk Scsi Partition
Dr Label Type Size Ctr Size Usage B:ID:L Offset:Size
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Volume 10MB None 0:02:0 64.0KB: 10.0MB
As the example shows, there are no changes to the container list display as a result of clearing the container.
Related Information
container Commands:
task Commands:
container create mirror
To create a mirror set from a single-partition volume set and freespace, use the container create mirror command. Any data on the original volume set remains intact during mirror creation and the user sees no interruption in service.
Command Availability
This command is supported on the following operating systems:
If you created a mirror set on a NetWare server, you must run the list devices command on the NetWare console and then create the necessary NetWare disk partitions and volumes.
For information on how to create partitions and volumes, see the appropriate NetWare documentation.
For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User's Guide.
Syntax
container create mirror [/wait{=boolean}]
[/io_delay{=integer}] {container} {scsi_device}
Parameters
{container}
Specifies the ID number (0 to 63) of the container on which to create a mirror set. You create a mirror set from a single-partition volume set.
{scsi_device}
Specifies the ID for the SCSI device whose freespace you want to use for mirroring the volume set specified in the container parameter. A SCSI ID consists of a SCSI channel number (e.g., 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive). See the installation guide for your controller to determine the number of channels it actually supports.
See the scsi_device section on page 3-8 for more information on how to specify the SCSI device.
Switches
/wait{=boolean}
Specifies whether to create the mirror set synchronously. If you set this switch to TRUE, the command prompt does not return until the mirror-set creation completes. If you set this switch to FALSE, the mirror-set creation starts asynchronously and the command prompt returns immediately.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/io_delay{=integer}
Specifies the number of milliseconds the controller waits between the I/Os required to create the mirror set. If you do not specify this switch, the I/O delay is always zero (0). The I/O delay value is not preserved between reboots of the operating system.
This switch is supported on the following operating systems:
Examples
Before creating 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 volume set) on this controller prior to the time the mirror set is created:
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 10MB NTFS 0:02:0 64.0KB: 10.0MB
The following example shows how to create a mirror set synchronously from volume set 0 using freespace on SCSI device (0,3,0):
AFA0> container create mirror /wait /io_delay=10 0 (0,3,0)
Executing: container create mirror /wait=TRUE /io_delay=10 0
(BUS=0, ID=3,LUN=0)
As the command executes, note the title bar of the DOS window displays the status of the command. For example:
Stat:OK!Task:101,Func:MCR Ctr:0,State:RUN 97.2%
See CLI Status Information for detailed information on the status information that the command displays in the title bar as it executes the task.
Use the container list command after the container create mirror command completes execution to display information about the 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
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Mirror 10MB NTFS 0:02:0 64.0KB: 10.0MB
0:03:0 64.0KB: 10.0MB
The following list describes the changes to the display as a result of using the container create mirror command:
- The Type column displays a new container type, which in the example is Mirror instead of the previously displayed Volume.
- The State column displays Normal (instead of a blank) as the mirror state.
(Note that this column appears only if you specify the /full switch with the container list command.)
- The Scsi B: ID: L column displays the SCSI device IDs for the two halves of the mirror set.
- The Partition Offset:Size column displays the partition offset and size for the two halves of the mirror set.
- 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.
After creating a mirror set, you can manipulate it by using the
-
container split command to split a mirror set
-
container unmirror command to unmirror a mirror set
Related Information
container Commands:
disk Commands:
container create mmirror
To create a multilevel container of mirror sets from a multilevel container of single-partition volume sets and freespace, use the container create mmirror command. Typically, you use this command after promoting a volume set built from multiple partitions with the container promote command.
The container create mmirror command is fully dynamic. If you use this command, users will not see any change or experience any interruption in service. However, performance may be reduced.
Command Availability
This command is supported on the following operating systems:
Notes
When creating a multilevel container of mirror sets on a NetWare server, you specify the container IDs (as described in the Parameters section) for the containers from which you want to create the multilevel mirror set. If NetWare is using any of these containers, an appropriate message displays. This message indicates that one or more of the containers you specified is in use by NetWare. The message directs you to remove any NetWare volumes and partitions from these containers. You can then create a multilevel container of mirror sets on a NetWare server.
After you create a multilevel container of mirror sets on a NetWare server, you must run the list devices command on the NetWare console and then create the necessary NetWare disk partitions and volumes.
For information on how to create partitions and volumes, see the appropriate NetWare documentation.
For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User's Guide.
Syntax
container create mmirror [/io_delay{=integer}]
[/wait{=boolean}] {container} {scsi_device}
[{scsi_device}...]
Parameters
{container}
Specifies the ID number (0 to 63) of the container whose underlying volume sets the command converts to mirror sets. You create a multilevel container of mirror sets from a multilevel container of single-partition volume sets and freespace.
{scsi_device}
Specifies the ID for the SCSI device whose freespace you want to use to create the multilevel container of mirror sets. The size of this freespace should be greater than or equal to the size of the first underlying volume set. A SCSI ID consists of a SCSI channel number (e.g., 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive). See the installation guide for your controller to determine the number of channels it actually supports.
See the scsi_device section on page 3-8 for more information on how to specify the SCSI device.
{scsi_device}...
Specifies the IDs for additional SCSI devices whose freespaces you want to use to create the multilevel container of mirror sets. There must be sufficient contiguous space available on each specified device.
The number of SCSI devices you specify must be equal to the number of single-partition volume sets that make up the multilevel container of volume sets. The size of the freespace used is equal to its corresponding underlying volume set.
Switches
/io_delay{=integer}
Specifies the number of milliseconds the controller waits between the I/Os required to create the multilevel container of mirror sets. If you do not specify this switch, the I/O delay is always zero (0). The I/O delay value is not preserved between reboots of the operating system.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/wait{=integer}
Specifies whether to create the multilevel container of mirror sets synchronously or asynchronously. If you set this switch to TRUE, the command creates the multilevel container of mirror sets synchronously and the command prompt does not return until the mirror-set creation task completes.
If you do not specify this switch, the mirror-set creation starts asynchronously and the command prompt returns immediately.
This switch is supported on the following operating systems:
Examples
Before creating a multilevel container of mirror sets, use the container list command to obtain information about any existing containers. As the following example shows, container 0 is a volume set that consists of two underlying volume sets created with the container promote 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
-- ----- ------ ------ --- ------ ------- ------ -------------
F: 0 Volume 30MB NTFS
63 Volume 15MB 0:02:0 64.0KB: 15.0MB
62 Volume 15MB 0:03:0 64.0KB: 15.0MB
The following example shows how to create a multilevel container of mirror sets with the following characteristics:
- The container specified (0) is a multilevel container of volume sets that was previously created with the
container promote command.
- The freespace from SCSI devices (0,4,0), and (0,5,0) are used to mirror the underlying volume sets.
- The default I/O delay is taken.
- The multilevel container of mirror sets is created asynchronously.
AFA0> container create mmirror 0 (0,4,0) (0,5,0)
Executing: container create mmirror 0 (BUS=0,ID=4,LUN=0)
(BUS=0,ID=5,LUN=0)
As the command executes, note the title bar of the DOS window displays the status of the command. For example:
Stat:OK!Task:101,Func:MCR Ctr:63,State:RUN 97.2%
See CLI Status Information for detailed information on the status information that the command displays in the title bar as it executes the task.
Use the container list command after using the container create mmirror command to display information about the multilevel container of mirror sets:
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 30MB NTFS
63 Mirror 15MB 0:02:0 64.0KB: 15.0MB
0:04:0 64.0KB: 15.0MB
62 Mirror 15MB 0:03:0 64.0KB: 15.0MB
0:05:0 64.0KB: 15.0MB
The following list describes the change to the display as the result of creating a multilevel container of mirror sets with the container create mmirror command:
- The Dr column is blank to indicate that the newly created mirror sets (63 and 62) do not have a drive letter assigned to them. You cannot assign a drive letter to an underlying container.
- The Type column displays Mirror for containers 63 and 62 to indicate that the underlying containers are mirror sets.
- The State column displays the state of the containers, which in this example are all in the Normal state.
(Note that this column appears only if you specify the /full switch with the container list command.)
- The Scsi B:ID:L column displays the SCSI device ID for the disk(s) on which the underlying mirror set(s) reside. In the example, mirror set 63 resides on disk 0:02:0 and 0:04:0. Mirror set 62 resides on disk 0:03:0 and 0:05:0.
- The Partition Offset:Size column displays the partition offset(s) and size(s) for the underlying mirror set(s). In the example mirror set 63 and 62 have partition offsets of 64.0 KB and sizes of 15.0 MB.
- 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 create mstripe
To create a multilevel stripe set from equally sized containers, use the container create mstripe command. The top level of a multilevel stripe container can only be a stripe set. You can create the following types of multilevel stripe set:
- A stripe set of mirror sets
- A stripe set of volume sets
- A stripe set of stripe sets
Note that a stripe set of RAID-5 sets is not allowed.
Command Availability
This command is supported on the following operating systems:
Notes
When creating a multilevel container of stripe sets on a NetWare server, you specify the container IDs (as described in the Parameters section) for the containers from which you want to create the multilevel stripe set. If NetWare is using any of these containers, an appropriate message displays. This message indicates that one or more of the containers you specified is in use by NetWare. The message directs you to remove any NetWare volumes and partitions from these containers. You can then create a multilevel container of stripe sets on a NetWare server.
After you create a multilevel container of stripe sets on a NetWare server, you must run the list devices command on the NetWare console and then create the necessary NetWare disk partitions and volumes.
For information on how to create partitions and volumes, see the appropriate NetWare documentation.
For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User's Guide.
Syntax
container create mstripe [/chunk_size{=integer}]
[/label{=string}]{container} [{container}...]
Parameters
{container}
Specifies the ID number (0 to 63) of the container from which you want to create the multilevel stripe set.
{container}...
Specifies the ID number or numbers (0 to 63) of one or more containers from which you want to create the multilevel stripe set. You can use up to 16 containers to create a multilevel stripe set. All specified containers must be the same size as the first container parameter and separated by blank spaces.
Switches
/chunk_size{=integer}
Specifies the chunk size for the multilevel stripe set. Valid values are 8 KB, 16 KB, 32 KB, and 64 KB.
If you do not specify the switch, it defaults to 32 KB.
This switch is supported on the following operating systems:
/label{=string}
Specifies a label to be assigned to the newly created multilevel stripe set. You can specify a maximum of sixteen characters for the label.
If you do not specify the switch, it defaults to no label. If you do not specify a label, you can do so later by using the container set label command.
This switch is supported on the following operating systems:
Examples
Before creating a multilevel stripe set, use the container list command to obtain information about any existing containers. As the following example shows, there are two existing containers (mirror sets) on this controller at the time the multilevel stripe set is created.
These mirror sets were previously created with the container create mirror 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 Mirror 15MB None 0:02:0 64.0KB: 15.0MB
0:02:0 15.0MB: 15.0MB
1 Mirror 15MB None 0:03:0 64.0KB: 15.0MB
0:03:0 15.0MB: 15.0MB
The following example shows how to create a multilevel stripe set from two equally sized containers, using the default chunk size of 32 KB. In this example, the two equally sized containers are mirror sets:
AFA0> container create mstripe 0 1
Executing: container create mstripe 0 1
Container 0 created
On UNIX systems, the message displayed after you execute the container create mstripe command includes the special file associated with the newly created multilevel stripe set.
Use the container list command after using the container create mstripe command to display information about the multilevel stripe 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
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Stripe 30MB 0 32KB None
63 Mirror 15MB 0:02:0 64.0KB: 15.0MB
0:02:0 15.0MB: 15.0MB
62 Mirror 15MB 0:03:0 64.0KB: 15.0MB
0:03:0 15.0MB: 15.0MB
The following list describes the change to the display as the result of creating a multilevel stripe set with the container create mstripe command:
- The Num Label column displays the ID number (in the example, 0) of the newly created multilevel stripe set and (indented to the right) the ID numbers of the containers that make up the multilevel stripe set. In the example, containers 63 and 62 are the containers (mirror sets) that make up the multilevel stripe set.
- If you specify a label when creating the multilevel stripe set, it appears in this column. Because no label was specified when the multilevel stripe set was created, no label appears in the column.
- On UNIX systems, the special file associated with the multilevel stripe set also appears in this column.
- The Type column displays the type Stripe for the newly created multilevel stripe set. The Type column also displays the container type for the underlying containers. In the example, Mirror appears in the Type column to indicate that the containers that make up the multilevel volume set are mirror sets.
- The Total Size column displays the total size for the multilevel stripe set. This size is the total of all the underlying containers. In the example, the total size for container 0 (the multilevel stripe set) is the sum of the two underlying containers (30 MB).
- The Total Size column also displays the sizes of all the underlying containers. In the example, the size of container 63 (15.0 MB) and container 62 (15.0 MB) were specified when the mirror sets were created with the
container create mirror command.
- The Chunk Size column displays the chunk size specified for the multilevel stripe set. In this example, the display shows 32 KB, the default chunk size.
- The Usage column displays None
to indicate that the newly created multilevel stripe set does not have a file system on it. To create an NTFS or FAT file system on a container, use the container format command.
- The State column displays Normal for containers 0, 63, and 62 to indicate that the state of the container is normal.
(Note that this column appears only if you specify the /full switch with the container list command.)
- The Scsi B:ID:L column displays the SCSI device ID for the disk on which you created the multilevel stripe set. It also displays the SCSI device ID(s) for the disk(s) on which the container(s) that make up the multilevel stripe set reside. In the example, the display shows that container 63's partitions are on SCSI disk 0:02:0. Container 62's partitions are on SCSI disk 0:03:0.
- The Partition Offset: Size column displays the partition offset and the size of the containers that make up the newly created multilevel stripe set. In the example, the display shows that container 63 has partition offsets of 64.0 KB and 15.0 MB and sizes of 15.0 MB. Container 62 has partition offsets of 64.0 KB and 15.0 MB and sizes of 15.0 MB. You specify the partition offset and size when you create the container.
Related Information
container Commands:
container create mvolume
To create a multilevel volume set, use the container create mvolume command. You can create the following types of multilevel volume sets:
- A volume set of stripe sets
- A volume set of mirror sets
- A volume set of RAID-5 sets
- A volume set of volume sets
Command Availability
This command is supported on the following operating systems:
Notes
When creating a multilevel container of volume sets on a NetWare server, you specify the container IDs (as described in the Parameters section) for the containers from which you want to create the multilevel volume set. If NetWare is using any of these containers, an appropriate message displays. This message indicates that one or more of the containers you specified is in use by NetWare. The message directs you to remove any NetWare volumes and partitions from these containers. You can then create a multilevel container of volume sets on a NetWare server.
After you create a multilevel volume set on a NetWare server, you must run the list devices command on the NetWare console and then create the necessary NetWare disk partitions and volumes.
For information on how to create partitions and volumes, see the appropriate NetWare documentation.
For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User's Guide.
Syntax
container create mvolume [/label{=string}]
{container} [{container}...]
Parameters
{container}
Specifies the ID number (0 to 63) of the container from which you want to create the multilevel volume set.
{container}...
Specifies the ID (0 to 63) of one or more additional containers from which you want to create the multilevel volume set. You can use up to 16 containers. Typically, the additional containers you specify are the same type as the first container. For example, if the first container is a stripe set then any subsequent containers are also stripe sets.
Switches
/label{=string}
Specifies a label to be assigned to the newly created multilevel volume set. You can specify a maximum of sixteen characters for the label.
If you do not specify the switch, it defaults to no label. If you do not specify a label, you can do so later by using the container set label command.
This switch is supported on the following operating systems:
Examples
Before creating a multilevel volume set, use the container list command to obtain information about any existing containers. As the following example shows, there are two existing containers (stripe sets) on this controller at the time the multilevel volume set is created.
These stripe sets were previously created with the container create stripe 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 Stripe 45MB 32KB None 0:02:0 64.0KB: 15.0MB
0:03:0 64.0KB: 15.0MB
0:04:0 64.0KB: 15.0MB
1 Stripe 15MB 32KB None 0:05:0 64.0KB: 15.0MB
The following example shows how to create a multilevel volume set from two single containers (in the example, two stripe sets):
AFA0> container create mvolume 0 1
Executing: container create mvolume 0 1
Container 0 created
On UNIX systems, the message displayed after you execute the container create mvolume command includes the special file associated with the newly created multilevel volume set.
Use the container list command after using the container create mvolume command to display information about the multilevel container of volume sets after you create it, 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 60.0MB None
63 Stripe 45MB 32KB 0:02:0 64.0KB: 15.0MB
0:03:0 64.0KB: 15.0MB
0:04:0 64.0KB: 15.0MB
62 Stripe 15MB 32KB 0:05:0 64.0KB: 15.0MB
The following list describes the columns that contain information as a result of creating a multilevel volume set with the container create mvolume command:
- The Num Label column displays the ID number (in the example, 0) of the newly created multilevel volume set and (indented to the right) the ID numbers of the containers that make up the multilevel volume set. In the example, containers 63 and 62 are the stripe sets that make up the multilevel volume set.
- If you specify a label when creating the multilevel volume set, it appears in this column. Because no label was specified when the multilevel volume set was created, no label appears in the column.
- On UNIX systems, the special file associated with the multilevel volume set also appears in this column.
- The Type column displays the type name Volume for the newly created multilevel volume set. The Type column also displays the container type for the underlying containers. In the example, Stripe appears in the Type column to indicate that the containers that make up the multilevel volume set are stripe sets.
- The Total Size column displays the total size for the multilevel volume set. This size is the total of all the underlying containers. In the example, the total size for container 0 (the multilevel volume set) is the sum of the two underlying containers (60 MB).
- The Total Size column also displays the sizes of all the underlying containers. In the example, the size of container 63 (45 MB) and container 62 (15 MB) were specified when the stripe sets were created with the
container create stripe command.
- The Chunk Size column displays the chunk size for each of the containers that make up the multilevel volume set. You specify the chunk size when you create stripe sets and RAID-5 sets. In the example, the chunk size is 32 KB.
- The Usage column displays None
to indicate that the newly created multilevel volume set does not have a file system on it. To create an NTFS or FAT file system on a container, use the container format command.
- The Scsi B:ID:L column displays the SCSI device ID for the disk on which you created the multilevel volume set. It also displays the SCSI device ID(s) for the disk(s) on which the container(s) that make up the multilevel volume set reside. In the example, the display shows that container 63's partitions reside on three SCSI disks: 0:02:0, 0:03:0, and 0:04:0. Container 62's partition resides on SCSI disk 0:05:0.
- The Partition Offset: Size column displays the partition offset and the size of the containers that make up the newly created multilevel volume set. In the example, the display shows that container 63 has a partition offset of 64 KB and a size of 15 MB on each of the three SCSI disks. Container 62 has a partition offset of 64 KB and a size of 15 MB. You specify the partition offset and size when you create the container.
Related Information
container Commands:
container create raid5
To create a RAID-5 set, use the container create raid5 command. The RAID-5 set must have a minimum of three disks.
When creating the RAID-5 set, you must initialize the array parity by using either the scrub method or the clear method. You specify one of these methods by using the /scrub switch or the /clear switch.
Command Availability
This command is supported on the following operating systems:
If you created a RAID-5 set on a NetWare server, you must run the list devices command on the NetWare console and then create the necessary NetWare disk partitions and volumes.
For information on how to create partitions and volumes, see the appropriate NetWare documentation.
For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User's Guide.
Syntax
container create raid5 [/cache{=boolean}]
[/chunk_size{=integer}]
[/label{=string}][/scrub{=boolean}]
[/wait{=boolean}] [/clear{=boolean}] {free_space}
[{scsi_device}...]
Parameters
{free_space}
Specifies the SCSI device and its associated freespace used to create the RAID-5 set. See the free_space section on page 3-10 for more information on how to specify the freespace.
{scsi_device}...
Specifies one or more SCSI devices. A SCSI ID consists of a SCSI channel number (e.g., 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive). See the installation guide for your controller to determine the number of channels it actually supports.
See the scsi_device section on page 3-8 for more information on how to specify the SCSI device.
The command uses the freespace(s) from the SCSI device(s) you specify to create the RAID-5 set. The size that the command uses from these device(s) is identical to the one you specify in the free_space parameter. The minimum number of partitions in a RAID-5 set is 3, and the maximum number of partitions is 16.
Switches
/cache{=boolean}
Specifies whether to enable the container's raw container cache. You can use this switch only if a native operating system's file system (for Windows NT, the NTFS or FAT file system) resides on the container. If you do not want to enable the RAID-5 set's raw container cache when you create it, you can do so later by using the container set cache command. In fact, the container set cache command gives you more control in setting the NVRAM write-back cache.
If you set this switch to TRUE, the command causes the controller to:
- Enable the read-ahead cache setting for the specified container.
You should always enable the read-ahead cache to optimize performance, unless your application--which is unlikely--is doing completely random reads.
- Enable when protected the NVRAM write-back cache setting for the specified container. This means the controller enables the container's NVRAM write-back cache only if a battery is present and its status is OK.
This switch defaults to FALSE, which means the command causes the controller to disable the container's raw container cache. If you accept the default, the command
- Disables the read-ahead cache
- Disables the NVRAM write-back cache
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/chunk_size{=integer}
Specifies the chunk size for the RAID-5 set. Valid values are 8 KB, 16 KB, 32 KB, and 64 KB.
If you do not specify a value for this switch, it defaults to 32 KB.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/label{=string}
Specifies a label to be assigned to the newly created RAID-5 set. You can specify a maximum of sixteen characters for the label.
If you do not specify the switch, it defaults to no label. If you do not specify a label, you can do so later by using the container set label command.
Note that this label 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.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/scrub{=boolean}
Specifies whether to set up the parity during RAID-5 creation by scrubbing the RAID-5 set. If you set this switch to TRUE, the command sets up the parity by scrubbing the RAID-5 set.
Although the drive is immediately available, it is not parity-protected until the background scrub action completes.
This switch defaults to TRUE.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/wait{=boolean}
Specifies whether the command prompt returns only after the parity-protect operation completes. If you set this switch to TRUE, the command prompt returns only after the RAID-5 set is parity-protected, i.e., the scrub or zero action completes.
The default is FALSE (i.e., the command prompt returns immediately before the parity-protect operation completes).
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/clear{=boolean}
Specifies whether to set up the parity during RAID-5 creation by clearing the entire RAID-5 set. If you specify TRUE, the command sets up the parity during RAID-5 creation by clearing the RAID-5 set.
The default is FALSE (i.e., the command does not clear the entire RAID-5 set).
If you use neither this switch nor the /scrub switch, the command uses the scrub method by default.
Unlike the scrub method where the drive is immediately available, the clear method does not make the drive available for use until the parity-initialize operation completes.
If you specify TRUE for both the /scrub and /clear switches, the command displays an appropriate error message and returns to the AFA0> prompt.
This switch is supported on the following operating systems:
Examples
The following example creates a RAID-5 set with the following characteristics:
- Creates the RAID-5 set on four disk drives connected to bus 0
- Specifies a freespace of 10 MB
- Uses the scrub method
- Indicates the command prompt return only after the scrub operation completes
- Specifies a chunk size of 64 KB
- Accepts the default label
AFA0> container create raid5 /chunk_size=64K /scrub
((0,02,0),10M) (0,03,0) (0,04,0) (0,05,0)
Executing: container create raid5 /chunk_size=65,536
/scrub=TRUE ((BUS=0,ID=2,LUN=0),10,485,760 ) (BUS=0,ID=3,LUN=0)
(BUS=0,ID=4,LUN=0) (BUS=0,ID=5,LUN=0)
Container 0 created
As the command executes, note the title bar of the DOS window displays the status of the command. For example:
Stat:OK!Task:101,Func:R5S Ctr:0,State:RUN 84.6%
See CLI Status Information for detailed information on the status information that the command displays in the title bar as it executes the task.
On UNIX systems, the message displayed after you execute the container create raid5 command includes the special file associated with the newly created RAID-5 set.
Use the container list command after using the container create raid5 command to display information about the RAID-5 set.
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 RAID-5 30.0MB 64KB None 0:02:0 64.0KB: 10.0MB
0:03:0 64.0KB: 10.0MB
0:04:0 64.0KB: 10.0MB
0:05:0 64.0KB: 10.0MB
The following list describes the columns that contain information as a result of creating a RAID-5 set with the container create raid5 command:
- The Num Label column displays the ID number of the newly created RAID-5 set, which in the example is 0.
- If you specify a label when creating the RAID-5 set, it appears in this column. Because no label was specified when the RAID-5 set was created, no label appears in the column.
- On UNIX systems, the special file associated with the RAID-5 set also appears in this column.
- The Type column displays RAID-5 to indicate that the newly created container is a RAID-5 set.
- The Total Size column displays the total size of the freespace available. In this example, 40.0 MB of freespace was specified, which means that this column displays 30.0 MB as available.
- The Chunk Size column displays the chunk size you specified as the
chunk_size parameter, which in the example is 64 KB.
- The Usage column displays None
to indicate that the newly created RAID-5 set does not have a file system on it.To create an NTFS or FAT file system on a container, use the container format command.
- The State column displays the state of a container, which in the example shows Unprot to indicate that the RAID-5 set is not yet redundant. This means that the command has not completed the creation of the RAID-5 set. If the
container list command is executed after the RAID-5 set completes execution, the State column is blank.
(Note that this column appears only if you specify the /full switch with the container list command.)
- The Scsi B:ID:L column displays the SCSI device ID(s) for the disk(s) on which you created the RAID-5 set, which in the example are: 0:02:0, 0:03:0, 0:04:0, and 0:05:0.
- The Partition Offset: Size column displays the partition offset(s) and size(s) of the newly created RAID-5 set, which in the example is 64.0 KB and 10.0 MB respectively.
Related Information
container Commands:
container create stripe
To create a stripe set from freespace, use the container create stripe command.
Command Availability
This command is supported on the following operating systems:
If you created a stripe set on a NetWare server, you must run the list devices command on the NetWare console and then create the necessary NetWare disk partitions and volumes.
For information on how to create partitions and volumes, see the appropriate NetWare documentation.
For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User's Guide.
Syntax
container create stripe [/cache{=boolean}]
[/chunk_size{=integer}] [/label{=string}]
{free_space} [{scsi_device}...]
Parameters
{free_space}
Specifies the SCSI device and its associated freespace used to create the stripe set. See the free_space section on page 3-10 for more information on how to specify the freespace.
{scsi_device}...
Specifies one or more SCSI devices. A SCSI ID consists of a SCSI channel number (e.g., 0, 1, 2, 3, etc.), SCSI device ID (0 through 15 inclusive), and SCSI device logical unit number (0 through 7 inclusive). See the installation guide for your controller to determine the number of channels it actually supports.
See the scsi_device section on page 3-8 for more information on how to specify the SCSI device. The command uses the freespace(s) from the SCSI device(s) to create the stripe set. The size from the device is identical to the one you specify in the free_space parameter.
The minimum number of partitions for a stripe set is 2, and the maximum number is 16.
Switches
/cache{=boolean}
Specifies whether to enable the container's raw container cache.You can use this switch only if a native operating system's file system (for Windows NT, the NTFS or FAT file system) resides on the container. If you do not want to enable the stripe set's raw container cache when you create it, you can do so later by using the container set cache command. In fact, the container set cache command gives you more control in setting the NVRAM write-back cache.
If you set this switch to TRUE, the command causes the controller to
- Enable the read-ahead cache setting for the specified container.
You should always enable the read-ahead cache to optimize performance, unless your application--which is unlikely--is doing completely random reads.
- Enable when protected the NVRAM write-back cache setting for the specified container. This means the controller enables the container's NVRAM write-back cache only if a battery is present and its status is OK.
This switch defaults to FALSE, which means the command causes the controller to disable the container's raw container cache. If you accept the default, the command:
- Disables the read-ahead cache
- Disables the NVRAM write-back cache
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/chunk_size{=integer}
Specifies the chunk size for the stripe set. Valid values are 8 KB, 16 KB, 32 KB, and 64 KB.
If you do not specify a value for this switch, it defaults to 32 KB.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/label{=string}
Specifies a label to be assigned to the newly created stripe set. You can specify a maximum of sixteen characters for the label.
If you do not specify the switch, it defaults to no label. If you do not specify a label, you can do so later by using the container set label command.
Note that this label 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.
This switch is supported on the following operating systems:
Examples
Before creating a stripe set, use the disk show space command to obtain information about the available SCSI devices, as in the following example:
AFA0> disk show space
Executing: disk show space
Scsi B:ID:L Usage Size
----------- --------- -------------
0:00:0 Free 64.0KB: 11.0MB
0:01:0 Free 64.0KB: 11.0MB
0:02:0 Free 64.0KB: 49.0MB
0:03:0 Free 64.0KB: 49.0MB
0:04:0 Free 64.0KB: 49.0MB
0:05:0 Free 64.0KB: 49.0MB
0:06:0 Free 64.0KB: 11.0MB
0:08:0 Free 64.0KB: 11.0MB
The example list shows that there are eight SCSI disks available to create the stripe set. There must be enough contiguous freespace on all the specified drives.
The following example shows how to create a stripe set with the following characteristics:
- 15 MB of freespace on the (0,2,0) SCSI disk
- The default chunk size of 32 KB
- Two freespaces of 15 MB on the (0,3,0) and (0,4,0) SCSI disks
AFA0> container create stripe ((0,2,0), 15M) (0,3,0) (0,4,0)
Executing: container create stripe ((BUS=0,ID=2,LUN=0),15,728,640 )
(BUS=0,ID=3,LUN=0) (BUS=0,ID=4,LUN=0)
Container 0 created
On UNIX systems, the message displayed after you execute the container create stripe command includes the special file associated with the newly created stripe set.
Use the container list command after using the container create stripe command to display information about the stripe 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
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Stripe 45.0MB 32KB None 0:02:0 64.0KB: 15.0MB
0 Stripe 45.0MB 32KB None 0:02:0 64.0KB: 15.0MB
0:03:0 64.0KB: 15.0MB
0:04:0 64.0KB: 15.0MB
The following list describes the items in the display that contain information as the result of creating a stripe set with the container create stripe command:
- The Num Label column displays the ID number of the newly created stripe set, which in the example is 0.
- If you specify a label when creating the stripe set, it appears in this column. Because no label was specified when the stripe set was created, no label appears in the column.
- On UNIX systems, the special file associated with the container also appears in this column.
- The Type column displays the type
Stripe, to indicate that the newly created container is a stripe set.
- The Total Size column displays the size of the freespace that makes up the stripe set. In this example, the total size consists of the freespace (15.0 MB) specified with SCSI device (0,2,0) and equal sizes associated with SCSI devices (0,3,0), and (0,4,0) for a total of 45.0 MB.
- The Chunk Size column displays the chunk size you specified for the stripe set. In this example, the chunk size is the default (32 KB).
- The Usage column displays None
to indicate that the newly created stripe set does not have a file system on it. To create an NTFS or FAT file system on a container, use the container format command.
- The Scsi B:ID:L column displays the SCSI device ID(s) for the disk(s) whose associated freespaces you used to create the stripe set. In this example, the display shows 0:02:0, 0:03:0, and 0:04:0.
- The Partition Offset: Size column displays the partition offset(s) and the size(s) for the disk(s) whose associated freespaces you used to create the stripe set. In this example, the display shows 64.0KB:15MB, 64.0KB:15.0MB, and 64.0KB:15.0MB.
Related Information
container Commands:
disk Commands:
container create volume
To create a volume set from freespace, use the container create volume command.
Command Availability
This command is supported on the following operating systems:
If you created a volume set on a NetWare server, you must run the list devices command on the NetWare console and then create the necessary NetWare disk partitions and volumes.
For information on how to create partitions and volumes, see the appropriate NetWare documentation.
For information on how to display the NetWare console remotely on the NT client running FAST, see the Flexible Array Storage Tool User's Guide.
Syntax
container create volume [/cache{=boolean}]
[/label{=string}] {free_space} [{free_space}...]
Parameters
{free_space}
Specifies the SCSI device and its associated freespace used to create the volume set. See the free_space section on page 3-10 for more information on how to specify the freespace.
{free_space}...
Specifies any additional SCSI devices and associated freespaces used to create the volume set. A volume set can have a maximum of 16 partitions (or freespaces, since each freespace becomes a partition).
Switches
/cache{=boolean}
Specifies whether to enable the container's raw container cache. You can use this switch only if a native operating system's file system (for Windows NT, the NTFS or FAT file system) resides on the container. If you do not want to enable the volume set's raw container cache when you create it, you can do so later by using the container set cache command. In fact, the container set cache command gives you more control in setting the NVRAM write-back cache.
If you set this switch to TRUE, the command causes the controller to
- Enable the read-ahead cache setting for the specified container.
You should always enable the read-ahead cache to optimize performance, unless your application--which is unlikely--is doing completely random reads.
- Enable when protected the NVRAM write-back cache setting for the specified container. This means the controller enables the container's NVRAM write-back cache only if a battery is present and its status is OK.
This switch defaults to FALSE, which means the command causes the controller to disable the container's raw container cache. If you accept the default, the command
- Disables the read-ahead cache
- Disables the NVRAM write-back cache
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/label{=string}
Specifies a label to be assigned to the newly created volume set. You can specify a maximum of sixteen characters for the label.
If you do not specify the switch, it defaults to no label. If you do not specify a label, you can do so later by using the container set label command.
Note that this label 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.
This switch is supported on the following operating systems:
Examples
Before creating a volume set, use the disk show space command to obtain information about the available SCSI devices, as in the following example:
AFA0> disk show space
Executing: disk show space
Scsi B:ID:L Usage Size
----------- --------- -------------
0:00:0 Free 64.0KB: 11.0MB
0:01:0 Free 64.0KB: 11.0MB
0:02:0 Free 64.0KB: 49.0MB
0:03:0 Free 64.0KB: 49.0MB
0:04:0 Free 64.0KB: 49.0MB
0:05:0 Free 64.0KB: 49.0MB
0:06:0 Free 64.0KB: 11.0MB
0:08:0 Free 64.0KB: 11.0MB
The example list shows that there are eight SCSI disks available to create the volume set.
The following example creates a volume set on SCSI disk (0,2,0) with a freespace of 15 MB:
AFA0> container create volume ((0,2,0), 15M)
Executing: container create volume ((BUS=0,ID=2,LUN=0),15,728,640)
Container 0 created
On UNIX systems, the message displayed after you execute the container create volume command includes the special file associated with the newly created volume set.
Use the container list command after executing the container create volume command to display information about the volume 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
-- ----- ------ ------ --- ------ ------- ------ -------------
0 Volume 15.0MB None 0:02:0 64.0KB: 15.0MB
The following list describes the columns that contain information as the result of creating a volume set with the container create volume command:
- The Num Label column displays the ID number of the newly created volume set, which in the example is 0.
- If you specify a label when creating the volume set, it appears in this column. Because no label was specified when the volume set was created, no label appears in the column.
- On UNIX systems, the special file associated with the container also appears in this column.
- The Type column displays Volume to indicate that the newly created container is a volume set.
- The Total Size column displays the value(s) specified in the
free_space parameter(s), which in the example is 15.0 MB.
- The Usage column displays None
to indicate that the newly created volume set does not have a file system on it. To create an NTFS or FAT file system on a container, use the container format command.
- The Scsi B:ID:L column displays the SCSI device ID for the disk on which you created the volume set, which in the example is 0:02:0.
- The Partition Offset: Size column displays the partition offset and the size of the newly created volume set's partition, which in the example are 64.0 KB and 15.0 MB. The size is the size you specified in the
free_space parameter(s).
Related Information
container Commands:
disk Commands:
container delete
To delete a container from the currently opened controller, use the container delete command.
Command Availability
This command is supported on the following operating systems:
Notes
If you are deleting a container on a NetWare system, you must first go to the NetWare console and remove the corresponding volume and partition. For information on how to perform these operations, see the appropriate NetWare documentation.
After you delete a container on a NetWare server, you must run the list devices command on the NetWare console so that the corresponding virtual disk is removed from the system's internal device table.
Syntax
container delete [/always{=boolean}]
[/unconditional{=boolean}]{container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to delete. The container can be any container on the controller.
You can never delete a container if files are open on it.
Switches
/always{=boolean}
Specifies whether to delete the container, even if it has a file system. If you specify TRUE, the command deletes the container even if it has a file system. If you specify FALSE, the command deletes the container only if it has no file system.
This switch defaults to FALSE. In both cases, all user files must be closed; the /always switch cannot override this restriction.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/unconditional{=boolean}
Specifies whether to delete the container, even if the container has open files on it. If you specify TRUE, the command deletes the container even if it has open files on it.
The switch defaults to FALSE (that is, the container delete command does not delete a container that has open files on it).
WARNING:
Unconditionally deleting a container that is in
use can cause a system crash under some circumstances.
This switch is supported on the following operating systems:
Examples
Before deleting a container, use the container list command to obtain information about any existing containers. As the following example shows, there is a container 0 (a multilevel volume set) on this controller:
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 40.0MB NTFS
63 Volume 10.0MB 0:02:0 64.0KB: 10.0MB
62 Volume 15.0MB 0:02:0 64.0KB: 10.0MB
61 Volume 15.0MB 0:04:0 64.0KB: 10.0MB
The following example shows how to delete container 0 using the /always switch to indicate a delete even though the container has a file system:
AFA0> container delete /always=TRUE 0
Executing: container delete /always=TRUE 0
Use the container list command after using the container delete command to confirm that the command actually deleted the specified container, as in the following example:
AFA0> container list
Executing: container list
No containers found.
Note that in the example, the deletion of container 0 caused the deletion of all the underlying (hidden) containers (containers 63, 62, and 61).
Related Information
container Commands:
Back to Contents Page
