Anyone having LVM problems in RHEL 4.0 (U4+)?

Which commands? EMC Software commands like powermt or symcli? Or all commands including native OS ?

Sorry I guess I was not specific enough. I meant LVM specific commands (e.g. vgscan, vggroup)

PowerPath and Navi commands are all good range rover all wood!

Correction. It now seems that PowerPath is getting an error on start-up referencing "vgscan" as well as LVM commands not working. Below is an example of the error:

# /etc/init.d/PowerPath start
Starting PowerPath:/etc/init.d/PowerPath: line 126: 4908 Segmentation fault /sbin/vgscan >/dev/null 2>&1
/etc/init.d/PowerPath: line 126: 4909 Segmentation fault /sbin/vgchange -a y >/dev/null 2>&1
done

PowerPath Version:
EMCpower.LINUX-4.5.1-022
NaviSphere Version:
naviagentcli-6.19.2.6.5-1
QLogic HBA's:
QLA2340's
Firmware:
3.03.18
Driver:
8.01.02-d4

Anyone seeing this error on start-up with the latest RedHat update?

I think you should use 1.47 version of bios for hba.

1.46 is well within the range for the support matrix. From the release notes from 1.46 to 1.47 there is not "much" in terms of fixes.

No hits in our knowledgebase for this.

I suggest you create a case with Redhat and/or EMC. If there is a patch out there which causes problems with powerpath then we would like to know about it.

LOL, Thanks we already have both open. I like this new forum because it gives me the ability to see how widespread this is. However (like most of stuff we run) we appear to be keeping up with our updates better than most people. What I can tell you so far is that RedHat has isolated this to the latest LVM + DEVMAPPER builds. I currently have a case open with EMC but that is slow going.

More to come.

Regards,
Shmac

Red Hat has verified that this is an issue and will be fixed in U5 (Update 5) on RHEL 4.0 boxes

Internal issue is: 106123

Once the U5 errata comes out you will see some kind of "fix" on the following packages:

device-mapper-1.02.12-3.test.ARCH.rpm
lvm2-2.02.13-1.test.ARCH.rpm
lvm2-cluster-2.02.13-1.test.ARCH.rpm

If you are seeing this issue contact Red Hat for the rpm's (They are not released to the public yet) and follow these steps:

Instructions

* Unmount any GFS volumes.
(Note: You may need to fuser -m / and kill off any processes using the filesystem.)
* Fully stop the cluster suite: { rgmanager | clvmd | fenced | cman | ccsd }
* rpm -e lvm2 lvm2-cluster --nodeps
* rpm -ivh lvm2*.rpm device-mapper*.rpm
* mv /etc/lvm/lvm.conf /etc/lvm/lvm.conf.dist
* cp /etc/lvm/lvm.conf.rpmsave /etc/lvm/lvm.conf
* Restart the cluster suite: { ccsd | cman | fenced | clvmd | rgmanager }

*** UPDATE ***
The following is a comment from the RedHat Issue tracker on this issue:

This is only observed on locking types 1 & 2. In /etc/lvm/lvm.conf, set locking_type=3 as a workaround until 4.5 is released.

You can continue to use the test packages but they aren't an official hotfix. Or you can try the workaround above on the U4 packages.

Regards,
Shmac

See last comment

shmac,

are you running Powerpath 4.5.1 on Redhat AS 4.0 U4 server ? I was looking at Powerpath 4.5.1 release notes and only saw U3 listed. I have yet to find a document that lists U4 being supported. Have you seen it ?

Thanks

The release documentation do not get update on every possible os, hardware change. If you check the PowerPath infrastructure software support matrix you will see the Red Hat 4 U4 does support PowerPath 4.5.1 on most configurations that supported Red Hat 4 U3. To be certain though, you will have to check the compatibility matrix for yourself.

From powerlink select the E-Lab Interoperability Navigator (Find it in the Support Menu)
Click the PDFs abd Guides tab and scroll down to Infrastructure Software and select PowerPath. This is how I found the document, it probably exists somewhere else as well.

Justin