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 747450

Summary: scsi_debug module num_parts creates a bad partition table
Product: Red Hat Enterprise Linux 6 Reporter: Brian Lane <bcl>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2CC: mlombard
Target Milestone: rc   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-20 13:38:24 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 Brian Lane 2011-10-19 20:24:20 UTC
Description of problem:
When passing num_parts=4 (or even =1) it creates a partition table that is invlid. This happens on s390x and possibly on ppc64. It works fine on x86 systems.


Version-Release number of selected component (if applicable):
Linux  2.6.32-207.el6.s390x #1 SMP Mon Oct 10 01:56:05 EDT 2011 s390x s390x s390x GNU/Linux


Steps to Reproduce:
1. modprobe scsi_debug num_parts=4
2. dmesg


Additional info:

dmesg output from modprobe scsi_debug num_parts=4

scsi_debug: host protection
scsi36 : scsi_debug, version 1.82 [20100324], dev_size_mb=8, opts=0x0
scsi 36:0:0:0: Direct-Access     Linux    scsi_debug       0004 PQ: 0 ANSI: 5
sd 36:0:0:0: Attached scsi generic sg1 type 0
sd 36:0:0:0: [sdb] 16384 512-byte logical blocks: (8.38 MB/8.00 MiB)
sd 36:0:0:0: [sdb] Write Protect is off
sd 36:0:0:0: [sdb] Mode Sense: 73 00 10 08
sd 36:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
 sdb: sdb1 sdb2 sdb3 sdb4
sdb: p1 ignored, start 536870912 is behind the end of the disk
sdb: p2 ignored, start 983040 is behind the end of the disk
sdb: p3 ignored, start 2031616 is behind the end of the disk
sdb: p4 ignored, start 3080192 is behind the end of the disk
sd 36:0:0:0: [sdb] Attached SCSI disk

Comment 2 RHEL Program Management 2011-10-25 05:48:42 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 3 Maurizio Lombardi 2013-11-20 13:38:24 UTC

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