From: Milan Broz <gmazyland@gmail.com>
To: Stephen Cousins <steve.cousins@maine.edu>, dm-crypt@saout.de
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [dm-crypt] trouble with dm-crypt and NFS: server hangs
Date: Thu, 20 Mar 2014 20:16:30 +0100 [thread overview]
Message-ID: <532B3E8E.5080406@gmail.com> (raw)
In-Reply-To: <CAMFqqRr+hDepUv8LGWbm_RSv=K4ApDbvbsaSAb44Qp1ZaJnNTQ@mail.gmail.com>
On 03/20/2014 03:48 PM, Stephen Cousins wrote:
> I am testing dm-crypt with a system that serves data over NFS. I'm
> finding that when serving the data over NFS4 it will go for a little
> while and then it will just stop copying and networking on the NFS
> server will stall out so that other connections to other parts of the
> storage (a non-dm-crypt volume) will become very laggy. Soon after
> canceling the copy the other connections resume back to normal.
>
> I have tried this on two different servers, one with a single disk
> with ZFS and another with a ZFS raidz2 pool and they both do the same
> thing. CPU doesn't seem to be an issue. Doing local copies is not a
> problem. That is, copying to/from these volumes made up of dm-crypted
> disks from other disks on the server have no problems.
>
> One system (the one with the RAID pool) is CentOS 6.4 and the other
> one is CentOS 6.5.
>
> I'm curious if anyone else has run into this before and if so, what
> can be done to make it work? I'm going to test to see if taking ZFS
> out of the equation helps. I haven't run into this with ZFS with
> disks without dm-crypt.
Hi,
unfortunately the dmcrypt code in Centos 6.x is not what is upstream
kernel (mainly because of per cpu processing changes upstream).
(It would be interesting if it is reproducible with upstream kernel,
but I guess it is not easy to test...)
I am adding cc to dm-devel list, maybe someone there could have some idea
how to help here.
Milan
>
> Thanks,
>
> Steve
>
>
>
> -- ________________________________________________________________
> Steve Cousins Supercomputer Engineer/Administrator
> Advanced Computing Group University of Maine System 244
> Neville Hall (UMS Data Center) (207) 561-3574
> <tel:%28207%29%20561-3574> Orono ME 04469
> steve.cousins at maine.edu <http://maine.edu>
WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <gmazyland-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Cousins
<steve.cousins-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>,
dm-crypt-4q3lyFh4P1g@public.gmane.org
Cc: device-mapper development
<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: trouble with dm-crypt and NFS: server hangs
Date: Thu, 20 Mar 2014 20:16:30 +0100 [thread overview]
Message-ID: <532B3E8E.5080406@gmail.com> (raw)
In-Reply-To: <CAMFqqRr+hDepUv8LGWbm_RSv=K4ApDbvbsaSAb44Qp1ZaJnNTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 03/20/2014 03:48 PM, Stephen Cousins wrote:
> I am testing dm-crypt with a system that serves data over NFS. I'm
> finding that when serving the data over NFS4 it will go for a little
> while and then it will just stop copying and networking on the NFS
> server will stall out so that other connections to other parts of the
> storage (a non-dm-crypt volume) will become very laggy. Soon after
> canceling the copy the other connections resume back to normal.
>
> I have tried this on two different servers, one with a single disk
> with ZFS and another with a ZFS raidz2 pool and they both do the same
> thing. CPU doesn't seem to be an issue. Doing local copies is not a
> problem. That is, copying to/from these volumes made up of dm-crypted
> disks from other disks on the server have no problems.
>
> One system (the one with the RAID pool) is CentOS 6.4 and the other
> one is CentOS 6.5.
>
> I'm curious if anyone else has run into this before and if so, what
> can be done to make it work? I'm going to test to see if taking ZFS
> out of the equation helps. I haven't run into this with ZFS with
> disks without dm-crypt.
Hi,
unfortunately the dmcrypt code in Centos 6.x is not what is upstream
kernel (mainly because of per cpu processing changes upstream).
(It would be interesting if it is reproducible with upstream kernel,
but I guess it is not easy to test...)
I am adding cc to dm-devel list, maybe someone there could have some idea
how to help here.
Milan
>
> Thanks,
>
> Steve
>
>
>
> -- ________________________________________________________________
> Steve Cousins Supercomputer Engineer/Administrator
> Advanced Computing Group University of Maine System 244
> Neville Hall (UMS Data Center) (207) 561-3574
> <tel:%28207%29%20561-3574> Orono ME 04469
> steve.cousins at maine.edu <http://maine.edu>
_______________________________________________
dm-crypt mailing list
dm-crypt-4q3lyFh4P1g@public.gmane.org
http://www.saout.de/mailman/listinfo/dm-crypt
next prev parent reply other threads:[~2014-03-20 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 14:48 [dm-crypt] trouble with dm-crypt and NFS: server hangs Stephen Cousins
2014-03-20 19:16 ` Milan Broz [this message]
2014-03-20 19:16 ` Milan Broz
2014-03-20 22:12 ` [dm-crypt] " Stephen Cousins
2014-03-20 22:12 ` Stephen Cousins
2014-03-27 17:56 ` [dm-crypt] " Stephen Cousins
2014-03-27 20:28 ` Arno Wagner
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=532B3E8E.5080406@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.com \
--cc=steve.cousins@maine.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.