Red Hat Bugzilla – Bug 27956
Disk Druid reports wrong disk size, negative free space
Last modified: 2007-04-18 12:31:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.72 [en] (Win98; U)
During a Fisher install, Disk Druid misreports the capacity of a Maxtor 40GB disk as only approx. 7 GB. It wouldn't let me create my desired
38GB partition. Since this was a showstopper for my installation, I removed the disk and partitioned it in another machine using cfdisk (no
problems here, cfdisk properly identified my disk as having 16 cylinders, 63 sectors per track, 79406 cylinders and 40,981,118,976 Bytes.)
After moving the partitioned disk back and rerunning the Fisher install, disk druid reports 16 heads, 63 sectors per track, 13,870 cylinders
(wrong!) and 6,826 MB (wrong!). My partition shows up correctly as 38,391MB, but as a result of the earlier miscalculation druid reports the
remaining free space as -31,565MB (negative, very wrong!). In spite of this I skipped partitioning in disk druid, and continued the installation
which finished without any further problems.
Steps to Reproduce:
1.Use disk druid to partition a Maxstore 40 GB disk
Actual Results: Disk Druid reports the disk size as 13,870 Cylinders (6,826 MB)
Expected Results: 79406 Cylinders (40,981,118,976 Bytes), as reported by cfdisk (this number appears credible)
I have several Maxtor 40GB (7200 rpm) disks. Although the retail box looks the same and the available disk space is always 40,981,118,976
Bytes (40GB, as advertised), some disks are 79,406 cyl / 16 heads / 63 sec per track while others are 4,982 cylinders / 255 heads / 63 sec
track. Only the former create the disk druid problem described above, the latter don't.
Fixed in CVS.
*** Bug 54305 has been marked as a duplicate of this bug. ***