Bug 120815 - GPT disk can't be handled by kernel-2.6.5-1.319
Summary: GPT disk can't be handled by kernel-2.6.5-1.319
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: ia64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-14 04:21 UTC by Shinya Narahara
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-05-03 07:26:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Shinya Narahara 2004-04-14 04:21:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:
kernel-2.6.5-1.319 can't handle partitions in GPT.
For example, 

# parted /dev/sda
(Omitted)
Using /dev/sda
(parted) print
Disk geometry for /dev/sda: 0.000-34732.890 megabytes
Disk label type: gpt
Minor   Start        End    Filesystem     Name    Flags
1         0.017    128.016  fat16                  boot
2       128.017   4224.016  ext3
3      4224.017   5248.016  linux-swap
4      5248.017  34732.874  ext3
(parted) quit

# mount /dev/sda2 /mnt/cdrom
mount: /dev/sda5 is not a valid block device

However the kernel can handle fine the MS-DOS disk label.


Version-Release number of selected component (if applicable):
kernel-2.6.5-1.319

How reproducible:
Always

Steps to Reproduce:
1.make gpt partitions by using parted
2.boot with kernel-2.6.5-1.319
3.mount partitions in gpt.


Actual Results:  mount: /dev/sda5 is not valid block device

Expected Results:  mounted normally.

Additional info:

GPT is used by Windows2003 Server, this is important to
support this. RHEL3 kernel(2.4.21-4.EL) can handle this,
but this kernel is based 2.6...

Comment 1 Arjan van de Ven 2004-05-03 07:26:33 UTC
fixed in rawhide, even though fedora core has no ia64 release.


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