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 1273306 - [Regression] Incorrect ID_WWN_WITH_EXTENSION
Summary: [Regression] Incorrect ID_WWN_WITH_EXTENSION
Keywords:
Status: CLOSED DUPLICATE of bug 1308795
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1289485
TreeView+ depends on / blocked
 
Reported: 2015-10-20 07:56 UTC by Gris Ge
Modified: 2016-02-16 11:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-16 08:23:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gris Ge 2015-10-20 07:56:50 UTC
Description of problem:

The system/udev code should use VPD83 NAA ID if VPD83 TGT(type 5) not found.
Code:
        systemd/src/udev/scsi_id/scsi_id.c
            scsi_id()
        systemd/src/udev/scsi_id/scsi_serial.c
            scsi_get_serial()
                do_scsi_page83_inquiry()
                    check_fill_0x83_id()
                        static const struct scsi_id_search_values id_search_list

But got this output:
===
$ sudo sg_vpd --page 0x83  /dev/disk/by-id/wwn-0x606c03f24ee65001|grep -A1 NAA
                                                 ^^^^^^^^^^^^^^^^
    designator type: NAA,  code set: Binary
        0x50014ee603f2606c
          ^^^^^^^^^^^^^^^^
$ udevadm info -q property /dev/disk/by-id/wwn-0x606c03f24ee65001|grep ID_WWN_
ID_WWN_WITH_EXTENSION=0x606c03f24ee65001
                      ^^^^^^^^^^^^^^^^^^
===

The correct VPD83 NAA ID above is: 0x50014ee603f2606c
But          ID_WWN_WITH_EXTENSION=0x606c03f24ee65001


Version-Release number of selected component (if applicable):
RHEL-7.2-20151015.0
systemd-219-19.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install OS on a server.
2. ls -l /dev/disk/by-id/ |grep wwn
3. sudo sg_vpd --page 0x83  /dev/disk/by-id/wwn-<WWN>|grep -A1 NAA

Actual results:
ID_WWN_WITH_EXTENSION is different from SCSI VPD83 NAA ID.

Expected results:
ID_WWN_WITH_EXTENSION use SCSI VPD83 NAA ID when VPD83 TGT ID not available.

Additional info:

Sounds like a big-endian vs little-endian issue to me.

Not sure a regression or not yet, still trying to reproduce this on other server.

Comment 1 Gris Ge 2015-10-21 02:52:37 UTC
Confirmed regression.

A ahci disk works well on RHEL 7.1, but got this issue once upgraded to 7.2.

Comment 3 Gris Ge 2015-10-21 03:23:40 UTC
Problem also found on mpt2sas disks.

Comment 12 Michal Sekletar 2016-02-16 08:23:22 UTC

*** This bug has been marked as a duplicate of bug 1308795 ***


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