Bug 43903
Summary: | anaconda needs to handle special cases as to the number of partitions on various block devices. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alexandre Oliva <aoliva> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DEFERRED | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | shishz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:48:01 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
Alexandre Oliva
2001-06-07 21:24:53 UTC
I think that the kernel can only address up to 16 partitions on an IDE drive. There is the problem that Disk Druid and fdisk will let you create more than 16 partitions...that is addressed in bug #44115. But this particular bug is more of a limitation of the kernel than anything else. Well, perhaps it can't address more than 16 partitions, but I don't have 16 partitions: I've got hda1 as an extended partition and hda5-18, and, after I created the devices, they started working. Perhaps this limitation is no longer present in kernel 2.4? I will try to reproduce this at work tomorrow, but I will be surprised if the kernel can talk to partitions above hd*16, considering that the devices in the /dev directory only go up to hd*16. I am unable to get the kernel to mount or otherwise communicate with partitions over hd*16. For example, I have partitions on an IDE drive /dev/hda1 - /dev/hda20. The kernel will not mount partitions above /dev/hda16. The error message I get when I try 'mount /dev/hda18 /mnt/foo' is: 'mount: special device /dev/hda17 does not exist' To me, this seems more like a limitation of the kernel than a bug with the installer. I have partitions hda1 and hda5-hda18. After mknoding /dev/hda17 and /dev/hda18, they worked fine. The only problem was that the installer didn't create the devices, and this is the problem I'm reporting. Perhaps having more than 16 partitions won't work, but I don't have more than 16 partitions, I have ``only'' 15, an extended partition and 14 logical ones. this will take a bit of work, I'll do it first thing next cycle. Known limits: ide: 64 minors scsi: 16 minors dac960: 8 minors ataraid: 16 minors i20: 16 minors cpqarray/cciss: 16 minors *** Bug 56874 has been marked as a duplicate of this bug. *** Deferred to future release. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |