From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu,  7 Oct 2010 10:32:35 +0200 (CEST)
Received: from int-mx09.intmail.prod.int.phx2.redhat.com
 (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22])
 by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o977mvG6013011
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
 for <dm-crypt@saout.de>; Thu, 7 Oct 2010 03:48:58 -0400
Received: from [10.36.11.175] (vpn2-11-175.ams2.redhat.com [10.36.11.175])
 by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 o977mukK017733
 for <dm-crypt@saout.de>; Thu, 7 Oct 2010 03:48:57 -0400
Message-ID: <4CAD7B67.70808@redhat.com>
Date: Thu, 07 Oct 2010 09:48:55 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <AANLkTi=f99_0Hqp2xUUbdLZ96EA3qqRKa-+BcmhThyzK@mail.gmail.com>
 <20101007033103.GB12780@tansi.org>
In-Reply-To: <20101007033103.GB12780@tansi.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] out of memory
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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