GNU bug report logs - #41577
automatic alignment

Previous Next

Full log

Message #10 received at 41577-close <at> debbugs.gnu.org (full text, mbox):

From: "Brian C. Lane" <bcl <at> redhat.com>
To: Harald Dunkel <harald.dunkel <at> aixigo.com>
Cc: 41577-close <at> debbugs.gnu.org
Subject: Re: bug#41577: automatic alignment
Date: Thu, 28 May 2020 16:57:32 -0700

On Thu, May 28, 2020 at 03:00:43PM +0200, Harald Dunkel wrote:
> Hi folks,
> 
> Finding a good alignment appears to be a pretty complex task, esp.
> for some RAID devices, so I wonder if this could be better supported
> in parted? The current
> 
> [bzzzzzzzz] The resulting partition is not properly aligned for best performance.
> 
> for all 2**n is *more* than annoying. For my lsi RAID I had to use
> 
> Number  Start  End           Size          File system  Name    Flags
>  1      1536s  46880782847s  46880781312s               export
> 
> following the guidelines on [1].
> 
> Obviously the align-check option has some deeper knowledge about
> a good alignment, but it doesn't tell. :-(

Yeah, it's complicated :) But if you use the latest parted it will tell
you more if you try to create a mis-aligned partition:

Start? 8s
End? 100%
Warning: You requested a partition from 4096B to 1074MB (sectors 8..2097151).
The closest location we can manage is 17.4kB to 1074MB (sectors 34..2097118).
Is this still acceptable to you?
Yes/No? y
Warning: The resulting partition is not properly aligned for best performance: 34s % 2048s != 0s
Ignore/Cancel?


This means that it needs to be multiples of 2048 sectors to be aligned
(this example is just an example with a disk image).

Brian

-- 
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.