Bug 177411
Summary: | LVM scans physical paths after mpio is set up | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Rod Nayfield <nayfield> |
Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | bmarzins, coughlan, jbrassow, nayfield |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-01-10 21:21:31 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: |
Description
Rod Nayfield
2006-01-10 14:06:18 UTC
Please supply: lvm.conf file output of 'lvm version' output of 'vgscan -vvvv' and also output of 'dmsetup info -c' and 'dmsetup table' (to show the multipath config) (my suspicion is that it's just the error message that needs fixing, but the code is actually doing the right thing) turns out that this might only be an issue when the LUN already has the LVM volume. For example, reinstalling the OS on the server. So what is probably happening is that the system scans (at boot) the physical paths. Later, the user logs in and configures multipathing. So in theory, a reboot might solve this. I am testing now (reinstalling). Ok so the issue is relatively minor. Only happens when multipath is not set up at boot, and then gets set up. Reboot fixes it. Is there a way to fix this short of a reboot? Without the diagnostics I asked for, I still don't know what the problem is. i.e. I don't know if the tools were or were not correct in displaying those error messages. |