Opened 3 years ago
Last modified 3 years ago
#17177 new bug
DriveSetup: creates malformed partition/table for certain sizes
Reported by: | jessicah | Owned by: | jessicah |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Partitioning Systems/GPT | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
It may be in GPT partitioning code rather than in DriveSetup itself, not entirely sure yet. Even after reboots, the partition layout reported in DriveSetup is still incorrect, so perhaps a malformed partition entry in GPT?
Noticed creating a partition of size 2n-1 would not show any free space for the disk. Sizes tested were 8191, 16383. Interestingly, 511 did not trigger it.
Note:
See TracTickets
for help on using tickets.