Specifications

DMMP Recovery Kit

Description

DMMP: Write issued on standby server can hang

If a write is issued to a DMMP device that is reserved on another server, then the IO can hang

indefinitely (or until the device is no longer reserved on the other server). If/when the device is

released on the other server and the write is issued, this can cause data corruption.

The problem is due to the way the path checking is done along with the IO retries in DMMP. When

"no_path_retry" is set to 0 (fail), this hang will not occur. When the path_checker for a device fails

when the path is reserved by another server (MSA1000), then this also will not occur.

Workaround: Set "no_path_retry" to 0 (fail). However, this can cause IO failures due to transient

path failures.

DMMP: Multiple initiators are not registered properly for SAS arrays that support ATP_C

LifeKeeper does not support configurations where there are multiple SAS initiators connected to an

SAS array. In these configurations, LifeKeeper will not register each initiator correctly, so only one

initiator will be able to issue IOs. Errors will occur if the multipath driver (DMMP for example) tries

to issue IOs to an unregistered initiator.

LifeKeeper on RHEL 6 cannot support reservations connected to an EMC Clariion

PostgreSQL Recovery Kit

Description

On SLES 10 SP2, the PostgreSQL resource hierarchy fails with error the database is not

running or has experienced a dbfail event

This issue is due to a SLES 10 SP2 kernel bug and has been fixed in update kernel version

2.6.16.60-0.23. On SLES 10 SP2, the netstat is broken due to a new format in /proc/<PID>/fd. The

netstat utility is used in the PostgreSQL recovery kit to verify that the database is running.

Solution:Please upgrade kernel version 2.6.16.60-0.23 if running on SLES 10 SP2.

SteelEye Protection Suite for Linux241