User`s guide

Release Notes
AA–RFBPE–TE 387372-005 Page 19
The maxcontig value is somewhat dependent on the number of units that are
active in your HSG80 configuration. In our testing, values of 128 and 256
blocks have worked very well. Your exact value will depend on the number of
storagesets in use. If your system is reporting excessive numbers of warnings
(ddi_iopb_alloc failed or fca_dma_zalloc failed) your value may be too high.
Both the maxcontig and rotdelay values can be set at the time of filesystem
creation with newfs flags or they can be modified at a later time using tunefs.
When using tunefs the filesystem must be unmounted. See the newfs(1M) and
tunefs(1M) man pages for further details.
7.17 Driver Messages
The driver initialization message may reference Solaris 2.5 and 2.6. This
message is incorrect and should be ignored.
The actual supported O/S levels are listed in Section 2.1 of this document.
7.18 Support for Dynamic Volume Expansion
Dynamic Volume Expansion is supported with this release. This allows you to
dynamically expand a storageset by concatenating another storageset of the same type
onto the end of the existing storageset, thereby increasing the size of the logical unit.
Refer to the HSG80 CLI Reference Guide for more information on configuring
concatsets.
Requirements:
• HSG80 ACS Version 8.5F
• Solaris 2.6 or 2.7
• Veritas File system, version 3.3
Current limitations:
• Concatsets are not supported by the SWCC client. You must use the CLI to
configure concatsets.
• A concatset may have only 1 or 2 members.
• If a concatset has 2 members, both members must be of the same storageset
type.
• A mirrorset cannot be used in a concatset (not as an entity or in a striped
mirrorset).
• The total number of disks in a concatset cannot exceed 24. For example, if a
14 member raid set exists, a 10 or less member raidset can be concatenated
with it.
• Entities added to concatsets must be initialized (have a unit or initialize