All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Problem when creating snashots
Date: Wed, 27 Sep 2006 12:36:21 +0200	[thread overview]
Message-ID: <451A5425.2010704@redhat.com> (raw)
In-Reply-To: <A544D1D7-C0A0-4EAB-8806-1A77B8453B56@gmail.com>

The problem with limited number of snapshots is caused by the using
big common mempool in dm-io module.
(This can happen even you have a lot of free memory...)

There are new dm-io patches which introduce new dm-io interface
(using private mempools) and solving this type of snapshot limitation.

Patches are currently in review and will probably change a bit,
but I hope it will in 2.6.19 kernel.

Milan

--
mbroz@redhat.com

The MoonSeeker napsal(a):
> Yes I really need it. I have to create a virtual network editor for my
> diploma project. So I have found many virtual solutions but the bestest
> for our project is OpenVZ. Unfortunatly, OpenVZ don't offer the copy on
> write with his solution, after many tests, I have found a solution based
> on LVM.
> 
> The main idea is to have a Virtual Private Server Core and lot of
> Virtual Private Server who are a snapshot of the Virtual Server Core.
> Now the problem is the limitation of VLM, I need more than 32 servers
> (32 snapshots). Will this limitation incresed in futur futur released of
> LVM? Or can we broke this limitation?
> 
> Have you a solution, it's relly urgent for me...
> 
> Thanks you
> 
> 
> Le 26 sept. 06 à 23:14, Jan Blunck a écrit :
> 
>> On Tue, Sep 26, The MoonSeeker wrote:
>>
>>> I'd like to create many snaphot of an image but I've got when I
>>> attemp to create the 32th snapshot :
>>>
>>> root@B03:/diplome# lvcreate -s -L150M -n 232 /dev/openvz/vps-core
>>>   Rounding up size to full physical extent 152.00 MB
>>>   device-mapper: reload ioctl failed: Ne peut allouer de la mémoire
>>>   Failed to suspend origin vps-core
>>>
>>> I don't understand the error..
>>
>> I'm not a native french speaker (hint!) but I assume you run out of
>> memory.
>>
>> Yes there are limitations to the number of snapshots. For every single
>> snapshot we have to allocate memory for copying the chunks to the
>> exception
>> store.
>>
>> Do you really need that many snapshots at the same time?
>>
>> -- 
>> dm-devel mailing list
>> dm-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/dm-devel
> 
> 
> -- 
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2006-09-27 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 15:08 Problem when creating snashots The MoonSeeker
2006-09-26 21:14 ` Jan Blunck
2006-09-27  9:51   ` The MoonSeeker
2006-09-27 10:36     ` Milan Broz [this message]
2006-09-27 10:55       ` The MoonSeeker
2006-09-27 11:45         ` Jan Blunck
2006-09-27 12:35         ` Milan Broz
2006-09-27 10:03 ` Bernd Zeimetz
2006-09-27 11:15   ` The MoonSeeker

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=451A5425.2010704@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-devel@redhat.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.