Bug 268581
Summary: | vgchange command fails to see volume group after installation of device-mapper-multipath-0.4.5-21.0.1.RHEL4.x86_64.rpm | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | bret goodfellow <bret.goodfellow> | ||||||
Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> | ||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Corey Marthaler <cmarthal> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 4.5 | CC: | agk, bmarzins, christophe.varoqui, dwysocha, egoggin, junichi.nomura, kueda, lmb, mbroz, prockai, tranlan | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | ia64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-01-12 21:10:55 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
bret goodfellow
2007-08-30 19:22:28 UTC
My target SAN (san attached to the D/R server) is a Hitachi 9570. The only changes between device-mapper-multipath-0.4.5-21.RHEL4 and device-mapper-multipath-0.4.5-21.0.1.RHEL4 were to the default configurations for devices. There was a change to some HITACHI device default configurations, which I assume is what you are seeing. The bugzilla that caused the change is bz #240075. You can verifty that this effects your device by looking at the files: # cat /sys/block/<device_node>/device/vendor and # cat /sys/block/<device_node>/device/model Where <device_node> is the device node name of one of the devices served up by your Hitachi 9570 (i.e. sda). If the vendor is "HITACHI" and the model starts with the letters "DF", then this will effect you. However the configuration change simply changes the priority callout program from a typo to the correct program name. Previously, the priority callout program was listed as /sbin/mpath/prio_hds_modular, which doesn't exist. It was changed to /sbin/mpath_prio_hds_modular, which does exist. You should check that /sbin/mpath_prio_hds_modular does actually exist on your system. If you are still seeing thins problem , could you please run the commands # multipath # multipath -ll with each package installed, and post the results for both in this bugzilla. Hello there, I checked out the files "vendor" and "model". They have the following in them: vendor: HITACHI model: DF600F The system doesn't have the patch on any more, since it corrupts our Disaster Recovery configuration. Not sure where to go from here. We have decided not to apply the multipath patch to any of our systems at this time until a resolution is provided. Can you check that /sbin/mpath_prio_hds_modular does exist on you system. Also, can you please send me a copy of /etc/multipath.conf and the output of running # multipath -v6 -ll Created attachment 244791 [details]
multipath.conf
Created attachment 244801 [details]
output from command: multipath -v6 -ll
Yes, the file "/sbin/mpath_prio_hds_modular" does exist. |