Bug 694253 - SCSI devices ordered differently between 6.1 snapshot-1 and snapshot-2
Summary: SCSI devices ordered differently between 6.1 snapshot-1 and snapshot-2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 846704
TreeView+ depends on / blocked
 
Reported: 2011-04-06 19:42 UTC by Daniel Yeisley
Modified: 2013-02-26 15:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-26 15:35:08 UTC
Target Upstream Version:


Attachments (Terms of Use)
dmesg boot log (46.01 KB, application/octet-stream)
2011-04-06 19:42 UTC, Daniel Yeisley
no flags Details
dmesg from kernel-2.6.32-128.el6.x86_64 (41.68 KB, application/octet-stream)
2011-04-06 19:44 UTC, Daniel Yeisley
no flags Details
/proc/partitions from kernel-2.6.32-125.el6.x86_64 (207 bytes, text/plain)
2011-04-06 19:50 UTC, Daniel Yeisley
no flags Details
/proc/partitions from kernel-2.6.32-128.el6.x86_64 (207 bytes, text/plain)
2011-04-06 19:51 UTC, Daniel Yeisley
no flags Details
/proc/scsi/scsi from kernel-2.6.32-125.el6.x86_64 (972 bytes, text/plain)
2011-04-06 20:54 UTC, Daniel Yeisley
no flags Details
/proc/scsi/scsi from kernel-2.6.32-128.el6.x86_64 (972 bytes, text/plain)
2011-04-06 20:55 UTC, Daniel Yeisley
no flags Details

Description Daniel Yeisley 2011-04-06 19:42:36 UTC
Created attachment 490370 [details]
dmesg boot log

Description of problem:
I'm seeing sda become sdb when I move from kernel-2.6.32-125.el6.x86_6 to kernel-2.6.32-128.el6.x86_64 on veritas[2,3].rhts.eng.bos.redhat.com.

Version-Release number of selected component (if applicable):
kernel-2.6.32-128.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install snapshot-1
2. Boot the system and look at /proc/partitions
3. Install kernel-2.6.32-128.el6.x86_64 and reboot
4. Check /proc/partitions again.
Or
1. Install snapshot-2 directly and check /proc/partitions.
  
Actual results:
With kernel-2.6.32-128.el6.x86_64 the megaraid boot device ends up being labeled sdb.  On all previous kernels I've tested it is sda.

Expected results:

Additional info:

Comment 1 Daniel Yeisley 2011-04-06 19:44:27 UTC
Created attachment 490371 [details]
dmesg from kernel-2.6.32-128.el6.x86_64

Comment 2 Daniel Yeisley 2011-04-06 19:50:24 UTC
Created attachment 490373 [details]
/proc/partitions from kernel-2.6.32-125.el6.x86_64

Comment 3 Daniel Yeisley 2011-04-06 19:51:01 UTC
Created attachment 490374 [details]
/proc/partitions from kernel-2.6.32-128.el6.x86_64

Comment 5 RHEL Program Management 2011-04-06 20:03:45 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 Daniel Yeisley 2011-04-06 20:54:11 UTC
Created attachment 490397 [details]
/proc/scsi/scsi from kernel-2.6.32-125.el6.x86_64

Comment 7 Daniel Yeisley 2011-04-06 20:55:04 UTC
Created attachment 490398 [details]
/proc/scsi/scsi from kernel-2.6.32-128.el6.x86_64

Comment 8 Daniel Yeisley 2011-04-19 19:05:50 UTC
So far I've only seen this on Dell PowerEdge 2850's and nowhere else.  I was able to reproduce it on veritas3.rhts.eng.bos.redhat.com, veritas2.rhts.eng.bos.redhat.com, and dell-pe2850-01.rhts.eng.bos.redhat.com.

Comment 9 RHEL Program Management 2011-10-07 15:29:34 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 10 Jes Sorensen 2013-02-26 15:35:08 UTC
SCSI device ordering is not guaranteed


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