[opensuse-factory] fdisk problem
![](https://seccdn.libravatar.org/avatar/6d198f8c8f1c94ccef873cebcf4f5dfa.jpg?s=120&d=mm&r=g)
Insists cylinder 2048 is the start of the disk. Same problem on x86_64. two weeks ago I returned a SDHC as bad because of the problem on 3 x86_64 boxes. Yesterday while partitioning a 160G IDE HD on the x86 I saw it again. I used cfdisk which worked.# rpm -qf /sbin/fdisk util-linux-2.18.91-10.1.i586 Size of HD is much less than it should be, e.g I couldn't set partition 1 to a size of 150G. cfdisk works. Bug #667514 submitted. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/25bbc96d9c53647354cb724e744b2222.jpg?s=120&d=mm&r=g)
On Wed, Jan 26, 2011 at 9:04 PM, Sid Boyce <sboyce@blueyonder.co.uk> wrote:
Insists cylinder 2048 is the start of the disk.
2048 sectors == 1 MiB That's the new standard offset for the first partition. I don't use fdisk that much anymore, but I suspect it is reporting the starting sector, not the starting cylinder. If it really is reporting cylinder 2048 and not sector 2048, that is a bug.
Same problem on x86_64. two weeks ago I returned a SDHC as bad because of the problem on 3 x86_64 boxes.
I suspect user error or fdisk bug, but not bad drives.
Yesterday while partitioning a 160G IDE HD on the x86 I saw it again. I used cfdisk which worked.# rpm -qf /sbin/fdisk util-linux-2.18.91-10.1.i586
Size of HD is much less than it should be, e.g I couldn't set partition 1 to a size of 150G.
G is not a valid unit for this discussion. You can use GB or GiB but they are different, so be sure to use the right one. Anyway, a manufacturer sells a 160 GB drive and Fdisk reports it as 150 GiB. Sounds right to me. ie. There is a 7% delta between GB and GiB. GB is the small unit so drive manufactures like to use it. It's like measuring in yards instead of meters because yards gives you a bigger number.
cfdisk works.
Curious. Maybe it reports GB not GiB? I can assure you a 160 GB drive only holds 150 GiB of data.
Bug #667514 submitted. Regards Sid.
Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/6d198f8c8f1c94ccef873cebcf4f5dfa.jpg?s=120&d=mm&r=g)
Pardon my slip, sector was the word I had been searching for. I've always used fdisk in the past, so it never occurred to me that the SDHC wasn't faulty. The penny dropped when I tried re-partitioning the HD. Definitely looks like a fdisk bug, cfdisk was totally OK. Regards Sid. On 27/01/11 04:36, Greg Freemyer wrote:
On Wed, Jan 26, 2011 at 9:04 PM, Sid Boyce<sboyce@blueyonder.co.uk> wrote:
Insists cylinder 2048 is the start of the disk.
2048 sectors == 1 MiB
That's the new standard offset for the first partition. I don't use fdisk that much anymore, but I suspect it is reporting the starting sector, not the starting cylinder.
If it really is reporting cylinder 2048 and not sector 2048, that is a bug.
Same problem on x86_64. two weeks ago I returned a SDHC as bad because of the problem on 3 x86_64 boxes.
I suspect user error or fdisk bug, but not bad drives.
Yesterday while partitioning a 160G IDE HD on the x86 I saw it again. I used cfdisk which worked.# rpm -qf /sbin/fdisk util-linux-2.18.91-10.1.i586
Size of HD is much less than it should be, e.g I couldn't set partition 1 to a size of 150G.
G is not a valid unit for this discussion. You can use GB or GiB but they are different, so be sure to use the right one.
Anyway, a manufacturer sells a 160 GB drive and Fdisk reports it as 150 GiB. Sounds right to me. ie. There is a 7% delta between GB and GiB. GB is the small unit so drive manufactures like to use it.
It's like measuring in yards instead of meters because yards gives you a bigger number.
cfdisk works.
Curious. Maybe it reports GB not GiB?
I can assure you a 160 GB drive only holds 150 GiB of data.
Bug #667514 submitted. Regards Sid.
Greg
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/ed90d0132a4f59f2d3a1cf82a1b70915.jpg?s=120&d=mm&r=g)
On Thu, 27 Jan 2011 05:59:34 +0000 Sid Boyce <sboyce@blueyonder.co.uk> wrote:
Pardon my slip, sector was the word I had been searching for. I've always used fdisk in the past, so it never occurred to me that the SDHC wasn't faulty. The penny dropped when I tried re-partitioning the HD. Definitely looks like a fdisk bug, cfdisk was totally OK.
Not a bug. SSDs need aligned partitions. Common wisdom is to start at a 1048576 byte offset to ensure this. Yes, this wastes 1MiB. No, this is not fatal with current storage capacities, especially considering the severe performance problems you get when not obeying proper alignment. cfdisk is probably just buggy and killing SSD performance. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/6d198f8c8f1c94ccef873cebcf4f5dfa.jpg?s=120&d=mm&r=g)
On 27/01/11 08:07, Stefan Seyfried wrote:
On Thu, 27 Jan 2011 05:59:34 +0000 Sid Boyce<sboyce@blueyonder.co.uk> wrote:
Pardon my slip, sector was the word I had been searching for. I've always used fdisk in the past, so it never occurred to me that the SDHC wasn't faulty. The penny dropped when I tried re-partitioning the HD. Definitely looks like a fdisk bug, cfdisk was totally OK.
Not a bug. SSDs need aligned partitions. Common wisdom is to start at a 1048576 byte offset to ensure this.
Yes, this wastes 1MiB. No, this is not fatal with current storage capacities, especially considering the severe performance problems you get when not obeying proper alignment.
cfdisk is probably just buggy and killing SSD performance.
I didn't try cfdisk on the 16GB SSD, there was no way I could make fdisk see more than 8GB. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Greg Freemyer
-
Sid Boyce
-
Stefan Seyfried