Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 801205

Summary:	minor device number change attempt fails
Product:	Red Hat Enterprise Linux 6	Reporter:	Corey Marthaler <cmarthal>
Component:	lvm2	Assignee:	Petr Rockai <prockai>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3	CC:	agk, dwysocha, heinzm, jbrassow, mbroz, msnitzer, prajnoha, prockai, thornber, zkabelac
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	lvm2-2.02.95-2.el6	Doc Type:	Bug Fix
Doc Text:	No documentation needed.	Story Points:	---
Clone Of:
Clones:	838562 (view as bug list)		Environment:
Last Closed:	2012-06-20 15:02:26 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 Corey Marthaler 2012-03-07 22:53:36 UTC

Description of problem:
This is a regression test failure on the first official 6.3 rpms.

 VOLUME MINOR DEV NUM CHANGE to 140 on taft-01
 taft-01: lvchange -ay -f -My --major 255 --minor 140 /dev/stripe_1_3131/stripe_1_31310

[root@taft-01 ~]# lvs -a -o +devices
 LV             VG            Attr     LSize   Devices
 stripe_1_31310 stripe_1_3131 -wi-a--- 904.00m /dev/sdh1(0)

[root@taft-01 ~]# lvchange -ay -f -My --major 255 --minor 140 /dev/stripe_1_3131/stripe_1_31310
  Error locking on node taft-01: Volume stripe_1_31310 (0:0) differs from already active device (253:2)
  Error locking on node taft-02: Volume stripe_1_31310 (0:0) differs from already active device (253:2)
  Error locking on node taft-04: Volume stripe_1_31310 (0:0) differs from already active device (253:2)
  Error locking on node taft-03: Volume stripe_1_31310 (0:0) differs from already active device (253:2)
  stripe_1_31310: reactivation failed

[root@taft-01 ~]# vgchange -an stripe_1_3131
  Error locking on node taft-01: Volume stripe_1_31310 (0:0) differs from already active device (253:2)
  Error locking on node taft-02: Volume stripe_1_31310 (0:0) differs from already active device (253:2)
  Error locking on node taft-04: Volume stripe_1_31310 (0:0) differs from already active device (253:2)
  Error locking on node taft-03: Volume stripe_1_31310 (0:0) differs from already active device (253:2)
  1 logical volume(s) in volume group "stripe_1_3131" now active


Version-Release number of selected component (if applicable):
2.6.32-220.4.2.el6.x86_64
lvm2-2.02.95-1.el6    BUILT: Tue Mar  6 10:00:33 CST 2012
lvm2-libs-2.02.95-1.el6    BUILT: Tue Mar  6 10:00:33 CST 2012
lvm2-cluster-2.02.95-1.el6    BUILT: Tue Mar  6 10:00:33 CST 2012
udev-147-2.40.el6    BUILT: Fri Sep 23 07:51:13 CDT 2011
device-mapper-1.02.74-1.el6    BUILT: Tue Mar  6 10:00:33 CST 2012
device-mapper-libs-1.02.74-1.el6    BUILT: Tue Mar  6 10:00:33 CST 2012
device-mapper-event-1.02.74-1.el6    BUILT: Tue Mar  6 10:00:33 CST 2012
device-mapper-event-libs-1.02.74-1.el6    BUILT: Tue Mar  6 10:00:33 CST 2012
cmirror-2.02.95-1.el6    BUILT: Tue Mar  6 10:00:33 CST 2012


How reproducible:
Everytime

Comment 4 Corey Marthaler 2012-03-08 23:28:30 UTC

This happens in single machine mode as well.

[root@taft-01 ~]# lvchange -ay -f -My --major 255 --minor 66 /dev/mirror_1_9514/mirror_1_95140
  Volume mirror_1_95140 (0:0) differs from already active device (253:6)
  mirror_1_95140: deactivation failed

Comment 5 Alasdair Kergon 2012-03-16 01:46:14 UTC

Peter has found the cause of this - a command-line argument processing mistake I made when reusing major/minor.  (I tested that it still found the arguments OK after the change but forgot to confirm their values were still correct...)

Easily fixed.

Comment 7 Corey Marthaler 2012-03-16 19:24:39 UTC

Fix verfied in the latest rpms.

2.6.32-251.el6.x86_64

lvm2-2.02.95-2.el6    BUILT: Fri Mar 16 08:39:54 CDT 2012
lvm2-libs-2.02.95-2.el6    BUILT: Fri Mar 16 08:39:54 CDT 2012
lvm2-cluster-2.02.95-2.el6    BUILT: Fri Mar 16 08:39:54 CDT 2012
udev-147-2.40.el6    BUILT: Fri Sep 23 07:51:13 CDT 2011
device-mapper-1.02.74-2.el6    BUILT: Fri Mar 16 08:39:54 CDT 2012
device-mapper-libs-1.02.74-2.el6    BUILT: Fri Mar 16 08:39:54 CDT 2012
device-mapper-event-1.02.74-2.el6    BUILT: Fri Mar 16 08:39:54 CDT 2012
device-mapper-event-libs-1.02.74-2.el6    BUILT: Fri Mar 16 08:39:54 CDT 2012
cmirror-2.02.95-2.el6    BUILT: Fri Mar 16 08:39:54 CDT 2012



VOLUME MINOR DEV NUM CHANGE to 197 on taft-01
taft-01: lvchange -ay -f -My --major 255 --minor 197 /dev/linear_2_957/linear_2_9570
verifying new minor num on taft-01

Comment 8 Peter Rajnoha 2012-04-12 13:41:03 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.

Comment 10 errata-xmlrpc 2012-06-20 15:02:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0962.html