All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Igor Yanover <igor.yanover@gmail.com>,
	device-mapper development <dm-devel@redhat.com>
Subject: Re: kcopyd_client_create allocation failure on creating snapshots
Date: Mon, 23 May 2005 10:48:09 -0400	[thread overview]
Message-ID: <1116859689.6218.18.camel@localhost.localdomain> (raw)
In-Reply-To: <ba31087e05052301254b142bbe@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 992 bytes --]

yes, i fired this while no further discussion found. i also want to know
any solution regarding this. 

ming

On Mon, 2005-05-23 at 10:25 +0200, Igor Yanover wrote:
>     Hi!
>     I've got the following error, while trying to create many
> snapshots ( > 32 ) :
> "device-mapper: : Could not create kcopyd client". After some digging,
> I found out that the reason is resize_pool() in dm-io.c trying to do
> mempool_resize that is probably too large. I've seen that the issue
> has been raised in this list before at:
> https://www.redhat.com/archives/dm-devel/2005-April/msg00080.html,
> with the same conclusions, but there was no discussion and as far I
> can seen, the code has not changed since. I understand that the
> correct fix would be to use per-kclient pools.
> Is anyone planning to work/already working on this?
> 
>      Thanks,
>           Igor
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2005-05-23 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23  8:25 kcopyd_client_create allocation failure on creating snapshots Igor Yanover
2005-05-23 14:48 ` Ming Zhang [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=1116859689.6218.18.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=dm-devel@redhat.com \
    --cc=igor.yanover@gmail.com \
    /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.