HP XP20000/XP24000 HP StorageWorks XP Disk Array Configuration Guide (T5278-96 - Page 99

Creating the file systems, Creating the mount directories

Get HP XP20000/XP24000 PDF manuals and user guides View all HP XP20000/XP24000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 99 highlights

7. Repeat this labeling procedure for each new device (use the disk command to select another disk). 8. When you finish labeling the disks, enter quit or press Ctrl-D to exit the format utility. For further information, see the System Administration Guide - Devices and File Systems at: http://www.oracle.com/technetwork/indexes/documentation. Creating the file systems 1. If you want to create a file system, create a file system of your choice on the given disks. For the various file systems you can set specific parameters that can have an impact on performance and are application-dependant. 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 rotdelay 0ms rps 90 # 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 can result in a loss of path failover in DMP. See "Installing and configuring the FCAs" (page 91) and the FCA 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 Configuring for use with Veritas Volume Manager 4.x and later 99

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
7.
Repeat this labeling procedure for each new device (use the
disk
command to select another
disk).
8.
When you finish labeling the disks, enter
quit
or press
Ctrl-D
to exit the format utility.
For further information, see the
System Administration Guide - Devices and File Systems
at:
h
t
tp://w
w
w
.o
r
ac
le
.co
m/t
ec
hne
t
w
o
r
k/inde
x
e
s/doc
ume
n
t
ati
o
n
.
Creating the file systems
1.
If you want to create a file system, create a file system of your choice on the given disks. For
the various file systems you can set specific parameters that can have an impact on performance
and are application-dependant.
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
rotdelay 0ms
rps
90
# 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 can result
in a loss of path failover in DMP. See
“Installing and configuring the FCAs” (page 91)
and the
FCA 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
Configuring for use with Veritas Volume Manager 4.x and later
99