disk image partition tables start at 2048 sectors (1M) not 16065

Bug #1367830 reported by Scott Moser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CirrOS
Fix Committed
Low
Unassigned

Bug Description

currently disk images (0.3.3 and previous) start at sector 16065.
This was probably done because fdisk would warn about not being on cylinder boundaries i'm guessing.

it would make more sense to start partition 1 on 2048.

Related bugs:
 * bug 1271205: kpartx / device-mapper errors on small disk

Scott Moser (smoser)
Changed in cirros:
status: New → Confirmed
importance: Undecided → Low
Scott Moser (smoser)
description: updated
Scott Moser (smoser)
description: updated
Revision history for this message
Scott Moser (smoser) wrote : Re: disk image partition tables start at 2048 sectors (1M) not not 16065

I believe this is fixed with the commit i made today to bin/part2disk (revno 349).
input to sfdisk is now specified in sectors (--unit=S) and is
 2048,,L,*

summary: - disk image partition tables start at 16065 not 2048
+ disk image partition tables start at 2048 sectors (1M) not not 16065
Scott Moser (smoser)
summary: - disk image partition tables start at 2048 sectors (1M) not not 16065
+ disk image partition tables start at 2048 sectors (1M) not 16065
Scott Moser (smoser)
Changed in cirros:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.