Solaris Volume Manager Parameters

md_mirror:md_resync_bufsz

Description

Sets the size of the buffer used for resynchronizing RAID 1 volumes (mirrors) as the number of 512-byte blocks in the buffer. Setting larger values can increase resynchronization speed.

Data Type

Integer

Default

The default value is 1024. Larger systems could use higher values to increase mirror resynchronization speed.

Range

128 to 2048

Units

Blocks (512 bytes)

Dynamic?

No

Validation

None

When to Change

If you use Solaris Volume Manager RAID 1 volumes (mirrors), and you want to increase the speed of mirror resynchronizations. Assuming that you have adequate memory for overall system performance, you can increase this value without causing other performance problems.

If you need to increase the speed of mirror resynchronizations, increase the value of this parameter incrementally (using 128-block increments) until performance is satisfactory. On fairly large or new systems, a value of 2048 seems to be optimal. High values on older systems might hang the system.

Commitment Level

Unstable

Change History

For information, see md_mirror:md_resync_bufsz.

md:mirrored_root_flag

Description

Overrides Solaris Volume Manager requirements for replica quorum and forces Solaris Volume Manager to start if any valid state database replicas are available.

The default value is disabled, which requires that a majority of all replicas are available and synchronized before Solaris Volume Manager will start.

Data Type

Boolean values

Default

0 (disabled)

Range

0 (disabled) or 1 (enabled)

Dynamic?

No

Validation

None

When to Change

Use of this parameter is not supported.

Some people using Solaris Volume Manager accept the risk of enabling this parameter if all three of the following conditions apply:

• When root (/) or other system-critical file systems are mirrored

• Only two disks or controllers are available

• An unattended reboot of the system is required

If this parameter is enabled, the system might boot with a stale replica that inaccurately represents the system state (including which mirror sides are good or in Maintenance state). This situation could result in data corruption or system corruption.

Change this parameter only if system availability is more important than data consistency and integrity. Closely monitor the system for any failures. You can mitigate the risk by keeping the number of failed, Maintenance, or hot-swapped volumes as low as possible.

For more information about state database replicas, see Chapter 6, State Database (Overview), in Solaris Volume Manager Administration Guide.

Commitment Level

Unstable