RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 976688 - multipath -w does not work as expected
Summary: multipath -w does not work as expected
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-multipath
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: yanfu,wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-21 07:57 UTC by Xiaowei Li
Modified: 2021-09-03 12:05 UTC (History)
6 users (show)

Fixed In Version: device-mapper-multipath-0.4.9-53.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-22 03:55:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Xiaowei Li 2013-06-21 07:57:38 UTC
Description of problem:


Version-Release number of selected component (if applicable):
device-mapper-multipath-0.4.9-51.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
# multipath -ll
mpathb (353333330000007d1) dm-2 Linux   ,scsi_debug      
size=1.0G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 32:0:0:1 sdc 8:32 active ready running
`-+- policy='service-time 0' prio=1 status=enabled

1. > /etc/multipath/wwids
2. multipath -W
successfully reset wwids
3. multipath -w mpathb
wwid '353333330000007d1' not in wwids file
4. cat /etc/multipath/wwids 
# Multipath wwids, Version : 1.0
# NOTE: This file is automatically maintained by multipath and multipathd.
# You should not need to edit this file in normal circumstances.
#
# Valid WWIDs:
/353333330000007d1/

workaround:
run multipath -W again, then multipath -w mpathb will work.

Actual results:
multipath -w fails to remove the wwid

Expected results:


Additional info:

Comment 2 Ben Marzinski 2013-06-26 16:05:55 UTC
Multipath wasn't seeking back to the start of the file after it truncated it.  I'll have a package with a fix shortly.

Comment 3 Ben Marzinski 2013-07-05 22:49:59 UTC
This has been fixed now

Comment 4 yanfu,wang 2014-01-22 03:55:21 UTC
It's verified by /kernel/storage/multipath/wwids in RHEL7.0 snap2/snap3 testing:
https://tcms.engineering.redhat.com/run/108940/?from_plan=7249


Note You need to log in before you can comment on or make changes to this bug.