Hide Forgot
Description of problem: 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}} 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.
there is a patter matching problem. It's now fixed in 1.3.3, which will be available in rawhide soon. Thanks your report.
FYI: sysreport-fdisk isn't really used anymore and could probably go away. We now use getpartinfo() in functions.
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. http://rhn.redhat.com/errata/RHBA-2004-094.html