Partitions must begin (and end) at track boundaries. Proposal 009 in iso2:technical_specification The deletion process of a ssd uses as the smallest unit a block (= 512 KB - also known as "erase block size" (EBS)). So the clean alignment of the partitions is very important for the optimal performance and life time. Therefore the alignment should be a multiple of the EBS. Without clean alignment a lot of unnecessary read / write /erase cycles are generated. Remarks: - using GPT is a possible solution - something like fdisk -H 32 -S 32 or fdisk -H 56 is a possible solution (I donât know diskdrake is working) - I think this prob is near by proposal 008 (4k-sector-drives) - it should be created one unique solution for all types of drives (I think for a normal hd ( < 2 TB) the alignment is not so important)
Blocks: (none) => 1994
CC: (none) => pterjanComponent: Release (media, process) => RPM PackagesSource RPM: (none) => drakxtools
This one will be automatically fixed once the "align on 1mb boundaries" patch got merged *** This bug has been marked as a duplicate of bug 1215 ***
Status: NEW => RESOLVEDCC: (none) => thierry.vignaudResolution: (none) => DUPLICATE
@tv: this was a feature specification bug for mageia 2, and was tracked by 1994, perhaps it would be better if this one would depend on 1215, rather than resolving this in duplicate, because the TRACKER is now not correct. also, i'm not sure if the fdisk/diskdrake/gparted/etc... programs will be fixed i'm reopening, but if i'm mistaken, you can re-resolve it, but add bug 1215 on tracker 1994 in that case.
Status: RESOLVED => REOPENEDCC: (none) => maarten.vanraesResolution: DUPLICATE => (none)
@ALIEN; can't you fix the tracker instead of reopening this bugreport ?
CC: (none) => dmorganec
well, i thought this was more than just the patch, and in any case, iiuc the patch is not yet applied. but if this is resolved and i'm wrong, just resolv it again, but don't hesitate to block the tracker in the duplicated issue.
Keeping only one BR, the one with patches *** This bug has been marked as a duplicate of bug 1215 ***
Status: REOPENED => RESOLVEDResolution: (none) => DUPLICATE
Blocks: 1994 => (none)