Red Hat Bugzilla – Bug 140849
"fdisk -l" broken when over 26 EMC Powerpath disks
Last modified: 2007-11-30 17:07:05 EST
On a machine with more than 26 EMC Powerpath disks: # cat /proc/partitions | grep emcpowera 234 0 2097152 emcpowera 20539 21244 334756 156980 212504 2040659 17741268 5676721 0 191080 5702061 234 1 2096451 emcpowera1 20477 20932 333804 156920 212503 2040659 17741266 5676701 0 191010 5702031 233 0 15728640 emcpowera 54 21 936 40 0 0 0 0 0 40 40 232 0 102400 emcpowera 150403 113 151402 49310 4 0 4 10 0 49310 49310 Only one of those "emcpowera" is really the "emcpowera" device, the others could be "emcpoweraa" and "emcpowerab". "fdisk -l" will read the /proc/partitions and get the device name from there, and as can be seen above, it gets truncated. So either fdisk needs to have a way to find which device corresponds to a major/minor (this information is given by /proc/partitions), or have the kernel not truncate those names.
The kernel needs to report correct info.
Heather, are you aware of this problem with long PowerPath device names? Do you have a workaround, or a fix?
*** This bug has been marked as a duplicate of 79086 ***
Reopening this bug because it's against RHEL3 (whereas 79086 is against RHEL2.1).
This is not fixed in the RHEL3 U4 kernel. Are there any planned fixes for this? I will attach fdisk -l output, /proc/partitions and output from the EMC command "sympd list" which lists all physical disks. Output from "df" shows the devices we are actually mounting which do not match with fdisk -l output.
Created attachment 109375 [details] df | grep emcpower
Created attachment 109376 [details] cat /proc/partitions
Created attachment 109377 [details] fdisk -l
Created attachment 109378 [details] /usr/symcli/bin/sympd list (EMC Powerpath physical disk inventory)
A fix for this problem has just been committed to the RHEL3 U6 patch pool this evening (in kernel version 2.4.21-34.EL). Propagating acks from bug 79086, which is now against RHEL3. *** This bug has been marked as a duplicate of 79086 ***
An advisory 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/RHSA-2005-663.html