Bug 91617 - fdisk run on only md0, md1 and md5 instead of /dev/md{0,1,2,3,4,5,6,7,8,9,1{0,1,2,3,4,5}}
fdisk run on only md0, md1 and md5 instead of /dev/md{0,1,2,3,4,5,6,7,8,9,1{0...
Product: Red Hat Linux
Classification: Retired
Component: sysreport (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-05-25 23:23 EDT by Nick Urbanik
Modified: 2007-04-18 12:54 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-05-26 07:26:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nick Urbanik 2003-05-25 23:23:38 EDT
Description of problem: fdisk run on only md0, md1 and md5 instead of

Version-Release number of selected component (if applicable): 1.3.1-2

How reproducible: Always

Steps to Reproduce:
1. Run sysreport on system with more raid systems than md0, md1 and md5
2. Examine output
3. Notice that fdisk is only run on md0, md1 and md5, not on the others
Actual results: output includes only fdisk results for md0, md1 and md5

Expected results: output for all md devices

Additional info: It's a minor shell scripting slip in
/usr/share/sysreport/sysreport-fdisk, where the line
/sbin/fdisk -l /dev/md[0-15]
does not expand to /dev/md{0,1,2,3,4,5,6,7,8,9,1{0,1,2,3,4,5}} as one might expect.
Comment 1 Ngo Than 2003-05-26 07:26:30 EDT
there is a patter matching problem. It's now fixed in 1.3.3, which will be
available in rawhide soon. Thanks your report.
Comment 2 Mike Gahagan 2003-07-17 18:31:45 EDT

sysreport-fdisk isn't really used anymore and could probably go away. We now use
getpartinfo() in functions.

Comment 3 John Flanagan 2004-04-21 21:09:11 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


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