SCF Reference Manual for the Storage Subsystem (G06.28+, H06.05+, J06.03+)

PROTECTDIRECTORY { CHECKPOINT | OFF | SERIAL }
is the type of protection to use for the disk volume directory:
Use a full-block checkpoint to protect directory writes.CHECKPOINT
Do not perform special write protection of the directory.OFF
A write to the directory also results in a serial write to the mirror disk, if available. If the mirror
disk is not available, a full-block checkpoint writes the directory. (Default)
SERIAL
NOTE: This attribute is only valid for 514 byte per sector disks:
• internal SCSI disks in S-series enclosures
• 45xx disks in modular disk subsystems
DP2 ignores this attribute for 512-byte-sector disks:
• disks in an FCDM disk drive enclosure
• ESS disks in an Enterprise Storage array
• SAS disks in an MSA70 or M8390-12CG disk enclosure
RECOVERYTIMEOUT number
specifies the number of seconds that the NonStop storage controller must wait for the device
to respond to a recovery I/O. If the device does not respond within the specified time, the
NonStop storage controller times out and aborts the I/O.
NOTE: This attribute only affects ESS (Enterprise Storage) disks.
Valid values are 0, 30, and 60 (seconds). A value of 0 causes DP2 to use an internal default
value. For the ADD command, the default value for RECOVERYTIMEOUT is 0.
REVIVEBLOCKS number
is not a valid attribute for objects on systems running G06.24 or later RVUs. You can use this
attribute only when you are altering objects over an Expand link and targeting a system that
uses an older version of the storage subsystem.
REVIVEINTERVAL number
is not a valid attribute for objects on systems running G06.24 or later RVUs. You can use this
attribute only when you are altering objects over an Expand link and targeting a system that
uses an older version of the storage subsystem.
REVIVEPRIORITY number
specifies the priority of a revive task that executes in the DP2 IOP.
During the process of reviving a mirrored disk volume, DP2 must perform the time-consuming
task of copying data from the STARTED half of the disk volume to the half that is in the REVIVE
substate.
The REVIVEPRIORITY attribute specification can lessen the impact of this task on system resources
by giving the task a lower priority. For example, if REVIVEPRIORITY is 50, the revive process
defers to new requests with a priority above 50. Specifying a lower priority value ensures that
the revive operation does not impact higher priority workloads, but it does lengthen the time
that the revive operation takes.
You can adjust the REVIVEPRIORITY value during the revive operation to speed or slow the
revive progress.
The minimum value for REVIVEPRIORITY is 0, and the maximum value is 199. The default value
is 0, which causes DP2 to use its internal default of 50
212 Storage Subsystem Commands