Bug 471369 - RHEL5: fdisk cannot create partition with starting beyond 1 TB
Summary: RHEL5: fdisk cannot create partition with starting beyond 1 TB
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: util-linux
Version: 5.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 553155 553157
TreeView+ depends on / blocked
 
Reported: 2008-11-13 10:17 UTC by Tomas Smetana
Modified: 2018-10-27 14:33 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-13 23:44:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Proposed patch (468 bytes, patch)
2008-11-13 10:27 UTC, Tomas Smetana
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0085 0 normal SHIPPED_LIVE util-linux bug fix update 2011-01-12 17:29:18 UTC

Description Tomas Smetana 2008-11-13 10:17:51 UTC
Description of problem:
fdisk can not create partition which starting cylinder beyond 1 TB.

How reproducible:
Always

Steps to Reproduce:
Create partition which starting cylinder beyond 1 TB.

Actual results:
Max partiton size is 1 TB.

Expected results:
Max partiton size is 2 TB.
2 TB is restriction of DOS partiton format.

Additional info:
There is similar report.

http://osdir.com/ml/linux.redhat.release.tikanga.beta/2007-01/msg00027.html

Comment 1 Tomas Smetana 2008-11-13 10:27:47 UTC
Created attachment 323429 [details]
Proposed patch

Comment 2 Karel Zak 2008-11-27 10:42:17 UTC
Note that the problem has been fixed in upstream tree.

Comment 4 RHEL Program Management 2009-03-26 16:56:03 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 5 Tomas Smetana 2009-03-30 07:11:38 UTC
Just a note: This was fixed in RHEL-4 already (bug #471372).

Comment 12 RHEL Program Management 2009-04-20 22:46:55 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 30 errata-xmlrpc 2011-01-13 23:44:14 UTC
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 therefore 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/RHBA-2011-0085.html


Note You need to log in before you can comment on or make changes to this bug.