Bug 155728
| Summary: | Support and limitations of >2TB devices needs to be spelled out | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Joshua Baker-LePain <joshua.bakerlepain> |
| Component: | Installation_Guide | Assignee: | Jack Reed <jreed> |
| Status: | CLOSED WONTFIX | QA Contact: | ecs-bugs |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.7 | CC: | akopps, cmc, Colin.Simpson, pbokoc, rajdeep, spacewar, the.ridikulus.rat, wolf |
| Target Milestone: | --- | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 16:13:24 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
Joshua Baker-LePain
2005-04-22 16:01:44 UTC
Will this be fixed in U1? Still not fixed in U4. An update would be apreciated. I waiting for any fix on this. I have expereinced the same issue recently with RHEL 4 U4. I waiting for any fix on this. I have experienced the same issue recently with RHEL 4 U4. (In reply to comment #5) > I waiting for any fix on this. I have experienced the same issue recently with > RHEL 4 U4. > I am also waiting for a solution. The biggest problem seams that it is not possible to boot from a drive bigger than 2TB !! I have such machines and i do want to use Linux. I'm also wating for this to be fixed. I have now got several Dell Poweredge systems where I can happily configure 5 x 750GB SATA disks onto the PERC Raid controller in RAID 5. The installer happily lets me partition the disk into a small /boot and the rest into an LVM and then add my partitions onto the LVM. The install goes through clean and then fails to boot on first reboot. My only work around is to stick 3 disks into a RAID 5 and 2 into a RAID 1. Stick the /boot on the RAID 1, LVM the rest of the RAID 1 and the RAID 5 together. Very messy and wasteful on disk space. But I can't think of anything better to do, the PERC only works at the whole drive level not partitions. Surely this should be documented in the release notes, (for the record this isn't in the Dell Red Hat release notes/install guide either). Or the installer should warn and refuse I'd have thought. Do lots of people not see this? And this isn't fixed in RHEL 5 either.... Grub2 does supposedly support booting from GPT partitions but this doesn't ship with RHEL5 (does the installer even create them?). Removing automation notification Moving to Don Also a problem in RHEL 5. There are still problems in Fedora 14, so I'm guessing that this probably isn't fixed in RHEL 6 either. The Fedora 14 installer recognizes my 7 TB RAID and shows that 7 TB is available, but won't let me create an LVM physical volume larger than 2TB. If I try to create two physical volumes on the same RAID, it won't let them be more than 2 TB total. Verified that RHEL 6 Anaconda won't let me put a GPT on a drive (using 3ware hardware RAID), and won't let me create an LVM physical volume larger than 2TB. Given that 3TB drives are now cheap, and that hardware RAID volumes can easily exceed 2TB even when using smaller drives, it really seems like it would be a good idea for RHEL to support it. Note that I do not necessarily need the ability to boot from a >2TB and/or GPT device, though that would be nice. 3ware (and perhaps other?) hardware RAID cards allow carving a smaller volume out specifically to deal with software that can't boot from a >2TB or GPT volume. Created a GPT on the RAID volume, and started RHEL 6 installation over. Anaconda is then willing to create >2TB PVs on the GPT volume. The next patch fixes the bestDiskLabelType selection and allow to use gpt instead of mbr on >2TB block devices:
---
--- anaconda-13.21.149.orig/platform.py>2011-11-04 19:53:03.000000000 +0400
+++ anaconda-13.21.149/platform.py<---->2012-04-28 11:36:30.716757626 +0400
@@ -166,7 +166,7 @@
labelType = self.defaultDiskLabelType
for lt in self.diskLabelTypes:
l = parted.freshDisk(device=device.partedDevice, ty=lt)
- if l.maxPartitionStartSector < device.partedDevice.length:
+ if l.maxPartitionStartSector > device.partedDevice.length:
labelType = lt
break
---
Please, apply.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |