Bug 187781
Summary: | kpartx: can not cleanly delete partition mapping | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Eddie Williams <eddie.williams> |
Component: | device-mapper-multipath | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | agk, bmarzins, christophe.varoqui, egoggin, junichi.nomura, kueda, lmb, mbroz, tranlan |
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-04-20 20:27:00 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
Eddie Williams
2006-04-03 16:03:46 UTC
By default, kpartx should insert a 'p' as a delimiter if the last charater in the device name is a number, otherwise it should use no delimiter. If you manually specified the partition delimiter when you created the device, you must also specify it when you remove the partition. So instead of running $ kpartx -d /dev/mapper/3600508b300902930a70a82d7daac002c run $ kpartx -d -p 'p' /dev/mapper/3600508b300902930a70a82d7daac002c If this is not the way that kpartx is working for you, please reopen the bug. Oh yeah, and if you want multipath to automatically create partitions with the 'p' delimiter, you can just modify the kpartx call in /etc/dev.d/block/multipath.dev When you remove the device with 'multipath -f', the partition will be removed as well, regardless of the delimiter. Also, you can use the user_friendly_names config file option to give the multipath devices names like mpath1, mpath2, etc. Since these names will always end in a number, the partitions will always have a 'p' delimiter in them. Also, these names are easier to remember and type out. However, while the mappings are persistent, they may be different across machines (for instance, say that mpath1 refers to the device formerly named 3600508b300902930a70a82d7daac002c on node1. While this will always be true on node1, on node2 it might be mpath2 that refers to the device named 3600508b300902930a70a82d7daac002c) To avoid this, after all the devices have been named by multipath, copy the /var/lib/multipath/bindings file from one machine to the others. then these bindings will be consistent across machines. |