beautypg.com

Fmt utility values – HP XP P9500 Storage User Manual

Page 96

background image

NOTE:

FCU version 01-01-42 or later is required for the FMT utility.

The FMT utility defines the size of the OPEN-x volume in cylinders. The maximum number of cylinders
allowed by FMT is shown in

Table 39

on page 96.

Table 39 FMT Utility Values

01-XX-YY/2x LUSE

1

n=number of volumes

2

01-XX-

YY/2x Not

LUSE

1

01-XX-

YY/ZZ

LUSE

1

01-XX-

YY/ZZ Not

LUSE

1

01-XX-47

or earlier

1

Emulation

Type

(min(Vc*n*128/96-7,
65534)

3

65534

Not suppor-
ted

Not suppor-
ted

Not suppor-
ted

OPEN-V

(min 3338*n-7, 65534)

3331

5818

3331

3331

OPEN-3

(min 9996*n-7, 65534)

9959

5818

5818

5818

OPEN-8

(min 10016*n-7, 65534)

10009

5818

5818

5818

OPEN-9

(min 19759*n-7, 65534)

19752

5818

5818

Not suppor-
ted

OPEN-E

(min 49439*n-7, 65534)

49429

5818

5818

Not suppor-
ted

OPEN-L

1

XX = 1 or 2; YY,x = number; ZZ<2x

2

For Solaris, the data cylinder must be less than or equal to 32767. When using a LUSE volume, the geometry parameter is

different, so the number of cylinders should be calculated as follows:
Cylinder (specified to FAL formatting) <= (A*B*C) / (15*96) − 5

A: Head (Geometry parameter)
B: Block/Track (Geometry parameter)
C: cylinder (Geometry parameter)

3

Vc = OPEN-V cylinder value (MAX.:49160 cylinders using FAL)

The FMT utility can be used on standard-size OPEN-x volumes and on Virtual LVI/LUN (VIR) volumes.

NOTE:

The VIR OPEN-

x devices can also be called custom volume size (CVS) devices (for example,

OPEN-3-CVS). When formatting a VIR OPEN-

x LU, use the number of cylinders defined for VIR minus

seven (for example, use 993 cylinders for a VIR device defined with 1000 cylinders). The cylinder
size is: one cylinder = 15 tracks, one track = 96 sub-blocks, one sub-block = 512 bytes.

Table

40

on page 96 shows the relation between block length and write available capacity per track. The

actual data capacity per cylinder = (write available capacity per track) × (15 tracks).

Table 40 Relation between Block Length and Write Available Capacity per Track

Write Avail-

able Data Per

Track (Bytes)

Block Length

by Allocater =

(A) (Bytes)

Write Avail-

able Data Per

Track (Bytes)

Block Length

by Allocater =

(A) (Bytes)

Write Avail-

able Data per

Track (Bytes)

Block Length

by Allocater =

(A) (Bytes)

(A) × 44

565 - 596

(A) × 22

1589 - 1684

(A) × 1

23477 - 32760

Using the Data Exchange Software

96