| 2014-09-10 16:32:52 |
Scott Moser |
bug |
|
|
added bug |
| 2014-09-10 16:32:59 |
Scott Moser |
cirros: status |
New |
Confirmed |
|
| 2014-09-10 16:33:03 |
Scott Moser |
cirros: importance |
Undecided |
Low |
|
| 2014-09-10 16:43:27 |
Scott Moser |
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. |
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 1367830: kpartx / device-mapper errors on small disk |
|
| 2015-05-27 19:16:36 |
Scott Moser |
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 1367830: kpartx / device-mapper errors on small disk |
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 |
|
| 2015-05-27 19:29:04 |
Scott Moser |
summary |
disk image partition tables start at 16065 not 2048 |
disk image partition tables start at 2048 sectors (1M) not not 16065 |
|
| 2015-05-27 20:13:07 |
Scott Moser |
summary |
disk image partition tables start at 2048 sectors (1M) not not 16065 |
disk image partition tables start at 2048 sectors (1M) not 16065 |
|
| 2016-06-29 14:35:24 |
Scott Moser |
cirros: status |
Confirmed |
Fix Committed |
|
