Table 4. Container State Items
Table 5. Task Types
| Task |
Meaning |
Clear |
A clear container task is running on the specified container. When the clear container task completes, the specified container is cleared. The clear container task runs as a result of using the container clear command. Or, this is a RAID-5 set create task with the clear method specified. The RAID-5 set create task with the clear method specified runs as a result of using the container create raid5 command with the /clear switch. |
Create |
A create mirror set or create multilevel mirror set task is running on the specified container. When the create mirror set or create multilevel mirror set task completes, the specified container is a mirror set or a multilevel container of mirror sets. The create a mirror set or create a multilevel mirror set task runs as a result of using the container create mirror or container create mmirror command. |
FmtFAT |
A container format FAT file system task is running on the specified container. The format FAT file system task runs as a result of using the container format command with the /file_system switch set to FAT. |
FmtNTFS |
A container format NTFS file system task is running on the specified container. The format NTFS file system task runs as a result of using the container format command with the /file_system switch set to NTFS. |
Rebuild |
A rebuild task is running on the specified container. Typically, the rebuild task runs when the controller rebuilds a redundant container (RAID-5 set, mirror set, or multilevel container of mirror sets). |
Reconfg |
A container reconfigure task is running on the specified container. When the container reconfigure task completes, the specified container becomes a different container (for example, from a volume set to a stripe set). The container reconfigure task runs as a result of using the container reconfigure command. |
Scrub |
A scrub task is running on the specified redundant container. When the scrub task completes, the specified redundant container has reconstructed data on one partition based on data found on the other partition (for mirror sets and multilevel containers of mirror sets). Or, the specified redundant container recalculates and replaces, if necessary, the parity information (for RAID-5 sets). The scrub task runs as a result of the container scrub command. The scrub task also runs as a result of the container create raid5 command with the /scrub switch specified. |
Verify |
A verify with no repair of bad blocks task is running on the specified SCSI disk. When the verify with no repair of bad blocks task completes, the specified SCSI disk's blocks were verified without repairing any detected defects. The verify with no repair of bad blocks task runs as a result of using the disk verify command without specifying the /repair switch. |
VfyRepl |
A verify with repair of bad blocks task is running on the specified SCSI disk. When the verify with repair of bad blocks task completes, the specified SCSI disk's blocks are verified with repairs. The verify with repair of bad blocks task runs as a result of using the disk verify command with the /repair switch. |
Zero |
A clear disk task is running on the specified SCSI disk. When the clear disk task completes, the specified SCSI disk is cleared (that is, all data is erased and cannot be recovered). The clear disk task runs as a result of using the disk zero command. |
The Done % Column
This column displays a running percentage value that indicates the progress of the currently running task. The display shows the percentage in tenths of a percent increments. The currently running task is complete when the Done % column displays 100%.
The Ent Column
This column displays the number of elements associated with each container. The maximum is 16 elements.
The Creation Date and Creation Time Columns
The Creation Date column displays the date on which you created the container. The following example shows an example of a date that can appear in this column:
082997
As the example shows, the command displays the date in the form mmddyy where
-
mm is a two-digit number that indicates the month in which you created the container. For example, 01 indicates the month of January, 12 indicates the month of December, and so forth.
-
dd is a two-digit number that indicates the day of the month in which you created the container. For example, 29 indicates the 29th day.
-
yy indicates the year you created the container. For example, 97 indicates the container was created in the year 1997.
The Creation Time column displays the time in 24-hour format at which you created the container. The following example shows an example of a time that can appear in this column:
11:55:49
As the example shows, the command displays the time in the form hhmmss where
-
hh is a two-digit number that indicates the hour at which you created the container.
-
mm is a two-digit number that indicates the minute at which you created the container.
-
ss is a two-digit number that indicates the second at which you created the container.
The Boot Device Column
This column displays a value that indicates whether the container resides on the boot device. An X appears in the column if the container resides on the boot device. Otherwise, if the container does not reside on the boot device, no value appears in the column.
The Boot Device column does not appear on UNIX systems.
The System Files Column
This column displays a value that indicates whether the container resides on the system device. An X appears in the column if the container resides on the system device. Otherwise, if the container does not reside on the system device, no value appears in the column.
Related Information
container Commands:
Disk Commands:
container lock
Caution:
Use the container lock command only under
the direction of technical support.
To lock a container into volatile memory space on the currently opened controller, use the container lock command. When a container is locked into volatile memory space, the container reconfigure command has no effect. A locked container cannot be moved, deleted, made read-only, or used to create a multilevel container.
Command Availability
This command is supported on the following operating systems:
Syntax
container lock {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to lock into volatile memory space.
Examples
Before locking 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 is blank:
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 example locks container 0 into volatile memory space:
AFA0> container lock 0
Executing: container lock 0
Use the container list command (with the /full switch) after using the container lock command to display information about the container you just locked, 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 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 list describes the change to the display as the result of locking a container (in this example, container 0) with the container lock command:
- The Lk column displays L (instead of a blank)
to indicate that the specified container is now locked.
Related Information
container Commands:
container move
To renumber a container, use the container move command. If another container already has the new number, the command returns an error.
Command Availability
This command is supported on the following operating systems:
Notes
A controller currently supports 24 visible containers. A visible container is a container that is visible to the operating system and users. Visible containers are identified with container IDs 0 through 23.
Container IDs 24 through 63 are reserved for hidden containers. A hidden container is a container that is not visible to the operating system and can only be used by other containers. (The container list command, however, displays hidden containers.)
The container move command does not prevent you from assigning a hidden container ID (24 through 63) to a visible container. If you assign a visible container with a hidden container ID (24 through 63), the operating system no longer sees the visible container. In general, when renumbering a visible container, use container IDs 0 through 23. When renumbering a hidden container, use container IDs 24 through 63.
Syntax
container move {container} {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to renumber.
{container}
Specifies the ID number (0 to 63) to assign to the container specified in the first container parameter.
Examples
Before renumbering 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
-- ----- ------ ------ --- ------ ------- ------ -------------
F: 0 Volume 20.0MB NTFS 0:02:0 64.0KB: 10.0MB
0:03:0 64.0KB: 10.0MB
The following example renumbers container 0 to container 5:
AFA0> container move 0 5
Executing: container move 0 5
Use the container list command after using the container move command to display information about the container you just renumbered, 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: 5 Volume 20.0MB NTFS 0:02:0 64.0KB: 10.0MB
0:03:0 64.0KB: 10.0MB
The following list describes the change to the display as the result of renumbering container 0 to container 5 with the container move command:
- The Num Label column displays ID number 5 instead of 0.
- This column also displays the label assigned to the container when the container was created. If no label was assigned to the container then no label appears in the column.
Related Information
container offline
To take a specified container offline, use the container offline command.
Command Availability
This command is supported on the following operating systems:
Syntax
container offline {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to take offline.
Examples
Before taking a container offline, use the container list command to obtain information about any existing containers. As the following example shows, there are two containers (both volume sets) 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
-- ----- ------ ------ --- ------ ------- ------ -------------
E: 1 Volume 100MB NTFS 3:02:0 200MB: 100MB
2 Volume 10.0MB None 3:02:0 300MB: 10.0MB
The following example takes container 2 offline:
AFA0> container offline 2
Executing: container offline 2
Use the container list command after using the container offline command to display information about the container you just took offline, 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
-- ----- ------ ------ --- ------ ------- ------ -------------
E: 1 Volume 100MB NTFS 3:02:0 200MB: 100MB
2 Volume 10.0MB UnCfged 3:02:0 300MB: 10.0MB
The following list describes the change to the display as the result of taking container 2 offline with the container offline command:
- The Usage column displays UnCfged instead of None.
To bring the container online again, use the controller rescan command. After using the controller rescan command, use the container list command and note that the Usage column no longer displays UnCfged.
Related Information
container promote
To create a multilevel volume set from a stripe set or volume set, use the container promote command. In this case, the resulting container is a container of single-partition volume sets, each of which has a single partition from the original container.
Typically, you use the container promote command as part of a process to provide fault tolerance for existing volume sets. After container promote is executed, use container create mmirror (which provides the fault tolerance) to make this container a container of mirror sets.
Notes
The container promote command differs from the container add_level command as follows:
- The
container create volume command creates a single-level container.
- If you use the
container add_level command and specify the ID for a single-level volume set, the result is a volume set with two partitions.
- If you use the
container promote command and specify the ID for a single-level volume set, the result is a multilevel volume set (a volume set with two volumes under it).
Command Availability
This command is supported on the following operating systems:
Syntax
container promote {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to promote into a multilevel container.
Examples
Before promoting a container to a multilevel container, 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 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 example promotes container 0 to a multilevel container:
AFA0> container promote 0
Executing: container promote 0
Use the container list command after using the container promote command to display information about the container you just promoted, 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
63 Volume 15.0MB 0:02:0 64.0KB: 15.0MB
62 Volume 15.0MB 0:03:0 64.0KB: 15.0MB
61 Volume 15.0MB 0:04:0 64.0KB: 15.0MB
The following list describes the change to the display as the result of promoting a container (in this example, container 0) with the container promote command:
- The Num Label column displays four container IDs: 0 (the container that was promoted to a multilevel volume set), 63 (one of the underlying volume sets), 62 (a second underlying volume set), and 61 (a third underlying volume set).
- This column also displays the label assigned to the container when the container was created. If no label was assigned to the container then no label appears in the column.
- The Type column displays the Volume container type for the three underlying volume sets.
- The Total Size column displays the sizes of the containers. Note that the underlying containers are each 15.0 MB and container 0's size is the total of the two underlying containers.
- The Scsi B:ID:L column displays the SCSI channel number, SCSI device ID, and SCSI logical unit number for the underlying containers. In the example, container 63 resides on disk 0:02:0, container 62 resides on disk 0:03:0, and container 61 resides on disk 0:04:0.
- The Partition Offset:Size column displays the offset and size for the underlying containers' partitions. In the example, containers 63, 62, and 61 have 64.0 KB offsets and 15.0 MB sizes.
- 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.
As stated previously, you can now use the container create mmirror command to make a promoted container a container of mirror sets.
Related Information
container Commands:
disk Commands:
container readonly
To change a container's read-write status to read-only status, use the container readonly command. Subsequent modifications to the data on the container are prohibited. To use the container readonly command, the container cannot be in use by any application.
Command Availability
This command is supported on the following operating systems:
Syntax
container readonly {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to make read-only.
Examples
Before making a container read-only, 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 RO column is blank:
AFA0> container list /full
Executing: container list /full=TRUE 0
Num Total Oth Chunk Scsi
Dr Label Type Size Ctr Size Usage B:ID:L RO
-- ----- ------ ------ --- ------ ------- -------- ----
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 RO column.
The following example changes container 0 from read-write status to read-only status:
AFA0> container readonly 0
Executing: container readonly 0
Use the container list command (with the /full switch) after using the container readonly command to display information about the container you just made read-only, 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 RO
-- ----- ------ ------ --- ------ ------- -------- ----
F: 0 Volume 10.0MB NTFS 0:02:0 RO
Note that the example eliminates some items in the container list display so that you can see an example of the RO column.
The following list describes the change to the display as the result of making a container (in this example, container 0) read-only with the container readonly command:
- The RO column displays RO (instead of a blank)
to indicate that the specified container is now read-only.
Related Information
container Commands:
container readwrite
To change a container's read-only status to read-write status, use the container readwrite command. Subsequent modifications to the data on the container are allowed. To use the container readwrite command, none of the container's files can be open.
Command Availability
This command is supported on the following operating systems:
Syntax
container readwrite {container}
Parameters
{container}
Specifies the ID number (0 to 63) of the container to make read-write.
Examples
Before making a container read-write, 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 RO column displays the value RO:
AFA0> container list /full
Executing: container list /full=TRUE
Num Total Oth Chunk Scsi
Dr Label Type Size Ctr Size Usage B:ID:L RO
-- ----- ------ ------ --- ------ ------- -------- ----
F: 0 Volume 10.0MB NTFS 0:02:0 RO
Note that the example eliminates some items in the container list display so that you can see an example of the RO column.
The following example changes container 0 from read-only status to read-write status:
AFA0> container readwrite 0
Executing: container readwrite 0
Use the container list command (with the /full switch) after using the container readwrite command to display information about the container you just made read-write, 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 RO
-- ----- ------ ------ --- ------ ------- -------- ----
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 RO column.
The following list describes the change to the display as the result of making a container (in this example, container 0) read-write with the container readwrite command:
- The RO column displays blank (instead of an RO)
to indicate that the specified container is now read-write.
Related Information
container Commands:
container reconfigure
To change the configuration of a container, use the container reconfigure command. The container reconfigure command allows you to perform the following operations:
- Transform a container from one type to another type
- You can transform a container from one type to another type. For example, you can transform a stripe set into a RAID-5 set. In this case, the stripe set changes to a RAID-5 set and remains the same size. You specify the appropriate switches that the
container reconfigure command provides to transform a container.
- Add more SCSI drives to a container
- You can add more SCSI drives to a container by specifying one or more SCSI devices. This action extends the container. The command uses the freespace(s) from the SCSI device(s) you specify to reconfigure the container.
- For example, you can extend a stripe set by specifying one or more SCSI devices. In this case, the stripe set grows, but remains a stripe set.
- Change a container's chunk size
- You can change a container's chunk size by specifying the appropriate switch with a valid chunk size. For example, you can change the chunk size of a stripe set from 16K to 32K.
- Change a container's partition size
- You can change a container's partition size by specifying the appropriate switch with a valid partition size. For example, you can change the partition size of a mirror set from 500 MB to 800 MB.
- Extend an existing file system
- You can extend an existing file system by specifying the appropriate switch. (The command extends the file system after completing the reconfigure operation.)
- Move partitions to other disks
- You can move a container's partitions to other disks by specifying the appropriate switches with a valid partition or partitions. For example, you can move three entries of a RAID-5 set to new disks.
You can combine the previously listed operations. See the Flexible Array Storage Tool User's Guide for more information on how to combine these operations.
Command Availability
This command is supported on the following operating systems:
Notes
Some reconfigure operations result in destination sizes slightly different than what you specified.
Syntax
container reconfigure [/chunk_size{=integer}]
[/extend_fs{=boolean}][/mirror{=boolean}]
[/partition_move{=boolean}]
[/partition_size{=integer}]
[/raid5{=boolean}][/raid10{=boolean}]
[/stripe{=boolean}] [/volume{=boolean}]
[/wait{=boolean}]{container} [{scsi_device}...]
Parameters
{container}
Specifies the ID number (0 to 63) of the container you want to reconfigure.
{scsi_device}...
Specifies one or more SCSI devices. Typically, you specify one or more SCSI devices when adding more drives to a container or moving a container's partitions. A SCSI ID consists of a SCSI channel number (for example, 0, 1, 2, 3, etc.), a SCSI device ID (0 through 15 inclusive), and a SCSI device logical unit number (0 through 7 inclusive). 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 reconfigure the container.
Switches
/chunk_size{=integer}
Specifies the changed chunk size for the container. You can specify chunk sizes for the following types of containers:
- RAID-5 set
- Multilevel stripe set:
- Stripe set of mirror sets
- Stripe set of volume sets
- Stripe set of stripe sets
Valid values are 8 KB, 16 KB, 32 KB, and 64 KB.
This switch is supported on the following operating systems:
/extend_fs{=boolean}
Specifies whether to extend the file system so that it occupies the entire reconfigured container. If you specify TRUE, the command adds no new freespace and extends the file system so that it occupies the entire reconfigured container. (The command extends the file system after completing the reconfigure operation.) If you specify FALSE, the command adds freespace to the reconfigured container and does not extend the file system to occupy the entire reconfigured container.
This switch defaults to FALSE.
This switch applies only to those multilevel volume sets on which an NTFS file system resides. If you extend an NTFS file system, you must reboot your system in order for the extension to take effect.
If you do not specify this switch, you can later extend the file system with the container extend file_system command. This switch is supported only on Windows NT.
/mirror{=boolean}
Specifies whether to reconfigure the existing container into a mirror set. If you specify TRUE, the command reconfigures the existing container into a mirror set. If you specify FALSE, the command does not reconfigure the existing container into a mirror set.
This switch defaults to FALSE.
This switch is supported on the following operating systems:
Specifies whether to move partitions instead of adding extra space (i.e., using additional disks). If you specify TRUE, the command moves partitions instead of adding extra space. If you specify FALSE, the command does not move partitions.
This switch defaults to FALSE.
This switch is supported on the following operating systems:
Specifies the partition size. All partitions must be the same size and you can specify only one partition per disk.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/raid5{=boolean}
Specifies whether to reconfigure the existing container into a RAID-5 set. If you specify TRUE, the command reconfigures the existing container into a RAID-5 set. If you specify FALSE, the command does not reconfigure the existing container into a RAID-5 set.
This switch defaults to FALSE.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/raid10{=boolean}
Specifies whether to reconfigure the existing container into a RAID-10 set. If you specify TRUE, the command reconfigures the existing container into a RAID-10 set. If you specify FALSE, the command does not reconfigure the existing container into a RAID-10 set.
This switch defaults to FALSE.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/stripe{=boolean}
Specifies whether to reconfigure the existing container into a stripe set. If you specify TRUE, the command reconfigures the existing container into a stripe set. If you specify FALSE, the command does not reconfigure the existing container into a stripe set.
This switch defaults to FALSE.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/volume{=boolean}
Specifies whether to reconfigure the existing container into a volume set. If you specify TRUE, the command reconfigures the existing container into a volume set. If you specify FALSE, the command does not reconfigure the existing container into a volume set.
This switch defaults to FALSE.
This switch is supported on the following operating systems:
- Windows NT
- NetWare
- UNIX
/wait{=boolean}
Specifies whether the command performs the container reconfiguration operation synchronously or asynchronously. If you set this switch to TRUE, the command performs the container reconfiguration operation synchronously, which means the command prompt does not return until the container reconfiguration operation completes. If you set this switch to FALSE, the command performs the container reconfiguration operation asynchronously, which means the command prompt returns immediately.
This switch is supported on the following operating systems:
Examples
Use the information provided in the Flexible Array Storage Tool User's Guide to determine how you want to reconfigure any existing containers. Also, use the container list command to obtain information about any existing containers.
As the following example shows, there is a container 0 (a mirror set) and a container 1 (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 Mirror 15.0MB None 1:02:0 64.0KB: 15.0MB
Tigris 1:03:0 64.0KB: 15.0MB
E: 1 Volume 15.0MB NTFS 1:00:0 64.0KB: 15.0MB
The following example reconfigures a volume set to a stripe set:
AFA0> container reconfigure /partition_size=1 /stripe 1
Executing: container reconfigure /partition_size=1 /stripe=TRUE 1
As the command executes, note that the title bar of the DOS window displays the status of the command. For example:
Stat:OK!Task:100,Func:RCF Ctr:1,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 reconfigure command to display information about the container you just reconfigured, 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 15.0MB None 1:02:0 64.0KB: 15.0MB
Tigris 1:03:0 64.0KB: 15.0MB
E: 1 Stripe 15.0MB NTFS 1:00:0 64.0KB: 15.0MB
The following list describes the change to the display as the result of reconfiguring a container (in this example, container 1) with the container reconfigure command:
- The Type column displays Stripe (instead of Volume)
to indicate that the specified container is now a stripe set instead of a volume set.
Related Information
container Commands:
Back to Contents Page
