Red Hat Bugzilla – Bug 178334
ksconfig doesn't allow HP (cciss) disk names
Last modified: 2007-11-30 17:07:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
The ksconfig GUI tool doesn't allow the user HP cciss disk names. For example, on a typical HPDL380 the disk are exposed to the OS with names like:
In this naming scheme the integer following the last c is the controller number and the integer following the last d is the disk number. In a kickstart script one can use "cciss/c0d0" and anaconda handles the situation correctly. The ksconfig GUI however will not allow the user to enter anything other than a name like "sdx" or "hdx". If one attempts to enter a cciss device name the GUI will not allow it and reset the field. These names should clearly be allowed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start the ksconfig tool
2. on the partition information section add a partition
3. choose the ondisk option
4. enter a cciss disk name like 'cciss/c0d0'
Actual Results: ksconfig disallows the entry and resets the field
Expected Results: 'cciss/c0d0' should be allowed, it is a legal value
cciss drives are found on virtually all HP modern x86 servers, this is a fairly common need
Fixed in rawhide and added to the proper RHEL update proposed list.
Chris, did you also get all the other wacky device names here? If not, we
should be sure to get those too -- ping me and I'll show you the ones we handle
Yes, I have added a variety of strange devices from looking through the
Documentation/devices.txt file that comes with the kernel.
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.