Creating The Mount Directories; Configuring For Use With Veritas Volume Manager 4.X And Later - HP XP20000/XP24000 Configuration Manual

2. If you want to create a UFS file system, you can create the file system using the newfs –C
maxcontig command to potentially achieve better performance. In most cases, the default
maxcontig value on Solaris is 128. maxcontig sets the number of file system blocks read in
read-ahead.
Example
# newfs -C 32 /dev/rdsk/c1t2d0s0
For OPEN-V devices, you should use 32 or a multiple of 64 (64, 128, 192) as the maxcontig
value. For OPEN-x (non OPEN-V) devices, you should use 6 or a multiple of 6 (12, 18, 24, 30)
as maxcontig.
The track size for OPEN-V is 256 KB, the stripe size 512 KB. The track size for fixed size OPEN-x
is 48 KB and the stripe size 384 KB. As the UFS block size is 8 KB, specifying a value of 32 for
OPEN-V (32*8 KB = 256 KB) or 6 for fixed size OPEN-x (6*8 KB = 48 KB) will match the track
size. Thus matching the track size or a multiple of the track size will optimize the I/O performance.
The maxcontig value that you choose depends on your applications, and you can change the
maxcontig parameter to a different value at any time.
Use the character-type device file (for example, /dev/rdsk/c1t2d0s0) as the argument.
3. When the confirmation appears, enter y for yes if the file name is correct. If the file name is not
correct, enter n and repeat the previous steps.
4. Repeat this procedure for each new OPEN-x device.
5. You may check and change the maxcontig parameter later with the fstyp and tunefs
commands as outlined in the following example:
# fstyp -v /dev/rdsk/c1t2d0s0 | grep maxcontig
maxcontig 128
# tunefs -a 32 /dev/rdsk/c1t2d0s0

Creating the mount directories

1. Create a mount directory for each device using the mkdir command.
2. Enter each device into the mount table by editing /etc/vfstab.
3. Use the mount -a command to auto-mount devices.
4. Use a df -k command to verify the devices auto-mounted.
Configuring for use with Veritas Volume Manager 4.x and
later
HP XP disk arrays are certified for VxVM support.
Be sure to set the driver parameters correctly when you install the FCA. Failure to do so may result in
a loss of path failover in DMP. See
manufacturer's instructions for setting specific FCA parameters.
VxVM 3.2 and later use ASL to configure the DMP feature and other parameters. The ASL is required
for all arrays. With VxVM 5.0 or later, the ASL is delivered with the Volume Manager and does not
rotdelay 0ms rps
"Installing and configuring the
90
FCAs" on page 15 and the FCA
XP Disk Array Configuration Guide: Solaris 25