Cryptsetup development
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: David J Iannucci <pelcgfrghczy@punchcutter.ml1.net>,
	cryptsetup@lists.linux.dev
Subject: Re: device-mapper: reload ioctl ... failed: No such file or directory
Date: Sun, 3 Nov 2024 00:34:38 +0100	[thread overview]
Message-ID: <962b6cfb-d47e-4284-b044-91dd38858e0a@gmail.com> (raw)
In-Reply-To: <12f16036-a407-4ca7-9708-1c0f751f5e5d@app.fastmail.com>

On 11/2/24 11:53 PM, David J Iannucci wrote:
> On Wed, Oct 30, 2024, at 01:10, Milan Broz wrote:
...

>> I expect that you have device-mapper udev rules properly installed.
> 
> I'm not sure - how can I check this? This is a fairly bare-bones Gentoo
> install and I'm not a big expert on everything that I should be, so that
> might have slipped through the cracks.
> 
> But...! I just found something... it seems I am running a systemd-udevd,
> which would not have been my choice... I have taken steps to keep
> systemd completely off my machine, so this is a surprise. Will consult
> Gentoo forums about this.

It is ok, udev is part of systemd project now, but can run without system
(I have it on my testing non-systemd Gentoo too - it is expected.)

>> Is there anything in syslog?
> 
> This is what comes out in /var/log/messages:
> 
> Nov  2 16:31:36 linux kernel: loop0: detected capacity change from 0 to 209715200
> Nov  2 16:31:36 linux kernel: device-mapper: table: 254:0: crypt: Error allocating crypto tfm
> Nov  2 16:31:36 linux kernel: device-mapper: ioctl: error adding target to table

Ok, *this* is the issue. Some kernel module is perhaps missing or misconfigured.

According to log, aes-xts-plain64 should be your image cipher.

Do you have aes, xts (and ecb, which xts internally use) kernel crypto modules compiled
and available?

Does "cryptsetup benchmark --cipher aes-xts" work?

If so, please send me tcryptDump "cryptsetup tcryptDump <your image>".

> p.s. I note that simple reply on this list goes only to the sender
>       rather than back to the list, which is maybe the way the list
>       prefers it? Though in my experience most tech lists like to keep
>       this kind of discussion on the list so that more eyes are on
>       things, and solutions are documented, but if that's not the case
>       here, kindly let me know and I'll use simple reply to individuals
>       from now on.

Yes, please always copy reply to list (unless it contain some private info).
This is default config for maillist server, just use reply to all.

Milan


  reply	other threads:[~2024-11-02 23:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1730260948-20104-mlmmj-67cc752c@lists.linux.dev>
2024-10-30  4:12 ` device-mapper: reload ioctl ... failed: No such file or directory David J Iannucci
2024-10-30  7:10   ` Milan Broz
2024-11-02 22:53     ` David J Iannucci
2024-11-02 23:34       ` Milan Broz [this message]
2024-11-09 23:31         ` David J Iannucci
2024-11-02 23:36       ` Michael Kjörling

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=962b6cfb-d47e-4284-b044-91dd38858e0a@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=cryptsetup@lists.linux.dev \
    --cc=pelcgfrghczy@punchcutter.ml1.net \
    /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