From nobody Thu Nov 23 12:37:49 2023
X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sbd1n2cSzz52CCt
	for <freebsd-questions@mlmmj.nyi.freebsd.org>; Thu, 23 Nov 2023 12:38:05 +0000 (UTC)
	(envelope-from fbsddev@bsd2.de)
Received: from servers.bsd2.de (servers.bsd2.de [IPv6:2a0a:51c0:0:155::2b])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
	 client-signature RSA-PSS (4096 bits) client-digest SHA256)
	(Client CN "servers.bsd2.de", Issuer "R3" (verified OK))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4Sbd1m3KRBz3N8N
	for <freebsd-questions@freebsd.org>; Thu, 23 Nov 2023 12:38:04 +0000 (UTC)
	(envelope-from fbsddev@bsd2.de)
Authentication-Results: mx1.freebsd.org;
	dkim=none;
	spf=pass (mx1.freebsd.org: domain of fbsddev@bsd2.de designates 2a0a:51c0:0:155::2b as permitted sender) smtp.mailfrom=fbsddev@bsd2.de;
	dmarc=none
Received: from servers.bsd2.de (servers.vpn [IPv6:fd11:13bc:e33d:ffff:0:0:200:20])
	by servers.bsd2.de (8.17.1/8.17.1) with ESMTPS id 3ANCbnB6078896
	(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO)
	for <freebsd-questions@freebsd.org>; Thu, 23 Nov 2023 13:37:51 +0100 (CET)
	(envelope-from fbsddev@bsd2.de)
Date: Thu, 23 Nov 2023 13:37:49 +0100
From: fbsddev@bsd2.de
To: freebsd-questions@freebsd.org
Subject: GEOM_ELI: Crypto request failed (ENOMEM)
Message-ID: <ZV9HnVPCO_4nR6Io@servers.bsd2.de>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-questions
List-Help: <mailto:questions+help@freebsd.org>
List-Post: <mailto:questions@freebsd.org>
List-Subscribe: <mailto:questions+subscribe@freebsd.org>
List-Unsubscribe: <mailto:questions+unsubscribe@freebsd.org>
Sender: owner-freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
X-Spamd-Result: default: False [-3.16 / 15.00];
	NEURAL_HAM_LONG(-1.00)[-1.000];
	NEURAL_HAM_SHORT(-0.99)[-0.992];
	NEURAL_HAM_MEDIUM(-0.97)[-0.973];
	R_SPF_ALLOW(-0.20)[+a];
	MIME_GOOD(-0.10)[text/plain];
	ONCE_RECEIVED(0.10)[];
	TO_DN_NONE(0.00)[];
	FROM_EQ_ENVFROM(0.00)[];
	DMARC_NA(0.00)[bsd2.de];
	R_DKIM_NA(0.00)[];
	ASN(0.00)[asn:48314, ipnet:2a0a:51c0::/32, country:DE];
	MIME_TRACE(0.00)[0:+];
	PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org];
	RCVD_COUNT_ONE(0.00)[1];
	FROM_NO_DN(0.00)[];
	RCPT_COUNT_ONE(0.00)[1];
	MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	RCVD_TLS_ALL(0.00)[];
	MID_RHS_MATCH_FROMTLD(0.00)[];
	ARC_NA(0.00)[]
X-Rspamd-Queue-Id: 4Sbd1m3KRBz3N8N
X-Spamd-Bar: ---

Writing data to a slow USB Stick ( <5MB/sec write, geli encrypted and mounted with noatime) I suddenly
got many of those errors:

>>>  Nov 23 13:07:49 xxxxxxxxxx kernel: GEOM_ELI: Crypto request failed (ENOMEM). label/usbstick.eli[WRIGEOM_ELI: Crypto request failed (ENOMEM). label/usbstick.eli[WRITE(offset=21922807808, length=32768)]

But the written data seems correct.
What's the problem and can it be safely ignored?