Bug 116699
Summary: | large block device (> 1TB) has negative size | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Peter J. Holzer <hjp> |
Component: | kernel | Assignee: | Don Howard <dhoward> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | riel |
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-09-12 16:55:32 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
Peter J. Holzer
2004-02-24 15:13:11 UTC
I think I found the relevant patch: ChangeLog-2.4.13 mentions: - Leonard Zubkoff: 2TB disk device fixes and the patch changes start_sect and nr_sects in struct hd_struct from long to unsigned long. (linux/include/linux/genhd.h). I applied only the changes to hd_struct and ignored all the changes in put_user calls (AFAICS they are only cosmetic, as an unsigned long has the same size as a signed long). This seems to do the trick. I can access the device and mount the filesystem (haven't tried more yet). I just noticed a strange behaviour in the current kernel (2.4.9-e.59smp): fdisk -l fails on the large device (a read from /dev/sdc returns 0 bytes), but the ext3 file system on /dev/sdc1 can be mounted and seems to work (I haven't tried to read all 1.6 TB, though). Is this issue still present in -e.70? I see that the mentioned fields in hd_struct are still signed, so I would expect that the problem persists. We upgraded the server in question to RHEL 3 a few months ago, so I can't check anymore, sorry. Since we seem to have been the only ones who ever tried to use devices > 1TB with RHEL 2.1 and we moved everything to RHEL 3 and later now, I guess the bug can be closed. Ah, after reviewing 2.1 product documentation, I noticed that 1TB is the supported limit for block devices in RHEL2.1. Moving to RHEL3 was your best bet. Thanks for the response. |