Installation guide

3-38
container Commands
/unconditional{=boolean}
Specifies whether to delete the array, even if the array has
open files on it. If you specify TRUE, the command deletes the
array even if it has open files on it.
The switch defaults to FALSE (that is, the container
delete command does not delete an array that has open files
on it).
WARNING: Unconditionally deleting an array that is in use
can cause a system crash under some circumstances.
Examples
Before deleting an array, use the container list command to
obtain information about any existing arrays. As the following
example shows, there is an array 0 (a multilevel volume set) on this
controller:
AAC0>container list
Executing: container list
Num Total Oth Stripe Scsi Partition
Dr Label Type Size Ctr Size Usage C: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 array 0 using the /
always switch to indicate a delete even though the array has a file
system:
AAC0>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 array, as in the following example:
AAC0>container list
Executing: container list
No containers found.
Note that in the example, the deletion of array 0 caused the deletion
of all the underlying (hidden) arrays (arrays 63, 62, and 61).