Bug 225593
Summary: | Unable to mount a dm device | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Sanjay Rao <srao> |
Component: | mkinitrd | Assignee: | Peter Jones <pjones> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | CC: | kzak |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-02-01 15:41:25 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
Sanjay Rao
2007-01-31 16:02:12 UTC
This should probably be against util-linux, not dasher. Reassigning. Can you show the results of "dmsetup table" ? [root@perf6 multipath]# dmsetup table mpath2: 0 142239510 multipath 0 0 1 1 round-robin 0 2 1 8:32 1000 8:96 1000 mpath1: 0 142264000 multipath 0 0 1 1 round-robin 0 1 1 8:16 100 VolGroup01-LogVol01: 0 4063232 linear 253:9 137953664 VolGroup01-LogVol00: 0 137953280 linear 253:9 384 mpath1p3: 0 16002 linear 253:7 63 VolGroup00-LogVol01: 0 4063232 linear 8:2 137953664 mpath5: 0 71119755 multipath 0 0 1 1 round-robin 0 2 1 8:80 1000 8:144 1000 mpath1p2: 0 142030665 linear 253:7 224910 VolGroup00-LogVol00: 0 137953280 linear 8:2 384 mpath4: 0 142239510 multipath 0 0 1 1 round-robin 0 2 1 8:64 1000 8:128 1000 mpath1p1: 0 208845 linear 253:7 16065 mpath3: 0 142239510 multipath 0 0 1 1 round-robin 0 2 1 8:48 1000 8:112 1000 mpath2p1: 0 142239510 linear 253:0 0 This is the mapping of the mpath devices to dm devices [root@perf6 mpath]# ls -l total 0 lrwxrwxrwx 1 root root 7 Jan 31 10:44 mpath1 -> ../dm-7 lrwxrwxrwx 1 root root 7 Jan 31 10:44 mpath1p1 -> ../dm-8 lrwxrwxrwx 1 root root 7 Jan 31 10:44 mpath1p2 -> ../dm-9 lrwxrwxrwx 1 root root 8 Jan 31 10:44 mpath1p3 -> ../dm-10 lrwxrwxrwx 1 root root 7 Jan 31 10:44 mpath2 -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 31 10:44 mpath3 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 31 10:44 mpath4 -> ../dm-3 lrwxrwxrwx 1 root root 7 Jan 31 10:44 mpath5 -> ../dm-4 Ok, and "dmsetup ls", please? [root@perf6 dev]# dmsetup ls mpath2 (253, 0) mpath1 (253, 7) VolGroup01-LogVol01 (253, 12) VolGroup01-LogVol00 (253, 11) mpath1p3 (253, 10) VolGroup00-LogVol01 (253, 6) mpath5 (253, 4) mpath1p2 (253, 9) VolGroup00-LogVol00 (253, 5) mpath4 (253, 3) mpath1p1 (253, 8) mpath3 (253, 2) mpath2p1 (253, 1) Ok, I don't think anything is going wrong here -- you can't mount /dev/mpath2 directly because it has a partition on it, which is mpath2p1. Do "parted /dev/mpath2 p" to see the partition table for more info on that. |