From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Cc: Chris Murphy <chris@colorremedies.com>
Subject: [dm-crypt] Re: misaligned ending sector, 4096-byte luks sector size can't be used
Date: Thu, 27 Jan 2022 14:21:19 +0100 [thread overview]
Message-ID: <5027f6e4-b278-5c0f-357d-d7d095f4fa74@gmail.com> (raw)
In-Reply-To: <20220125122055.GA29580@tansi.org>
On 25/01/2022 13:20, Arno Wagner wrote:
> On Mon, Jan 24, 2022 at 23:10:34 CET, Milan Broz wrote:
>> On 24/01/2022 18:07, Chris Murphy wrote:
> [...]
>> The whole idea of misaligned backup GPT at the end of device is broken.
>> We should not follow that with adding hacks when the easy solution
>> is just to align a partition properly.
>
> I fully agree to that. It is like having a virtual sector size and
> then selectively in some places only not sticking to it. Not smart
> and a gross KISS violation. And, of course, fundamental problems
> like this one should always be fixed were they are caused.
And it should be fixed in fdisk now:
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=921c7da55ec78350e4067b3fd6b7de6f299106ee
Not sure if parted is maintained these days, but it should follow this approach...
Milan
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next prev parent reply other threads:[~2022-01-27 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 12:20 [dm-crypt] Re: misaligned ending sector, 4096-byte luks sector size can't be used Arno Wagner
2022-01-27 13:21 ` Milan Broz [this message]
2022-01-27 18:18 ` Christoph Anton Mitterer
2022-01-27 22:32 ` Chris Murphy
2022-01-27 22:35 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2022-01-24 17:07 [dm-crypt] " Chris Murphy
2022-01-24 22:10 ` [dm-crypt] " Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5027f6e4-b278-5c0f-357d-d7d095f4fa74@gmail.com \
--to=gmazyland@gmail.com \
--cc=chris@colorremedies.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.