From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] out of memory
Date: Thu, 07 Oct 2010 09:48:55 +0200 [thread overview]
Message-ID: <4CAD7B67.70808@redhat.com> (raw)
In-Reply-To: <20101007033103.GB12780@tansi.org>
On 10/07/2010 05:31 AM, Arno Wagner wrote:
> On Wed, Oct 06, 2010 at 08:48:24PM -0400, Paul Dugas wrote:
>> I'm working with an up-to-date CENTOS-5 x86_64 machine connected via
>> ATA-over-Ethernet to a Coraid array. I have one drive in the array
I would say that the problem will be more caused by network
layer (ATAoE) than dm-crypt (or combination of these).
Anyway, dmcrypt in RHEL5 is not upstream, if it is reproducible,
please report it to Red Hat Bugzilla with all used packages
and configuration. Ideally with full OOM log also.
It will not get the highest priority (well, it is Centos :)
but I would like to check it later.
(It will be assigned to me anyway:-)
You can try iSCSI instead to check if it helps.
But it should basically work for any block device without OOM,
even with very low RAM.
In any case this is kernel problem, not cryptsetup one.
(And I hope I will have more time for dmcrypt/cryptsetup in next weeks.)
Milan
prev parent reply other threads:[~2010-10-07 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 0:48 [dm-crypt] out of memory Paul Dugas
2010-10-07 3:31 ` Arno Wagner
2010-10-07 7:48 ` Milan Broz [this message]
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=4CAD7B67.70808@redhat.com \
--to=mbroz@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox