From: Chris Murphy <lists@colorremedies.com>
To: Christoph Anton Mitterer <calestyo@scientia.org>
Cc: dm-crypt@saout.de
Subject: [dm-crypt] Re: misaligned ending sector, 4096-byte luks sector size can't be used
Date: Thu, 27 Jan 2022 15:32:14 -0700 [thread overview]
Message-ID: <CAJCQCtS9CpWACT-MYoGtCW+-ueYjxQXi8u8D1yXU6Ls0BmaOBw@mail.gmail.com> (raw)
In-Reply-To: <8f40ab0093b14a14109102f69043b5f904d95828.camel@scientia.org>
On Thu, Jan 27, 2022 at 3:29 PM Christoph Anton Mitterer
<calestyo@scientia.org> wrote:
>
> On Thu, 2022-01-27 at 14:21 +0100, Milan Broz wrote:
> >
> > 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...
>
>
> Does anyone know whether gdisk was affected?
It is affected, that's what kicked off this thread - I just forgot to
include the URL.
https://bugzilla.redhat.com/show_bug.cgi?id=2044107
--
Chris Murphy
_______________________________________________
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 22:35 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
2022-01-27 18:18 ` Christoph Anton Mitterer
2022-01-27 22:32 ` Chris Murphy [this message]
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=CAJCQCtS9CpWACT-MYoGtCW+-ueYjxQXi8u8D1yXU6Ls0BmaOBw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=calestyo@scientia.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).