From mboxrd@z Thu Jan 1 00:00:00 1970 From: Milan Broz Subject: Re: Problem when creating snashots Date: Wed, 27 Sep 2006 14:35:26 +0200 Message-ID: <451A700E.4030202@redhat.com> References: <77299A0E-4C81-4820-97BF-FB15B1A96FD6@gmail.com> <20060926211407.GA2915@hasse.suse.de> <451A5425.2010704@redhat.com> <3FCAF7B4-032A-421B-A061-DB4EA906138F@gmail.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <3FCAF7B4-032A-421B-A061-DB4EA906138F@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: device-mapper development List-Id: dm-devel.ids The MoonSeeker napsal(a): > Where can I find this patch? I'd like to test it.. >=20 Patches are in development quilt queue=20 http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/ related *testing* patches=20 dm-io-*.patch dm-kcopyd-newio.patch dm-exception-store-newio.patch but depends probably on some patches in series file. Note: there is no patch for new dm-io change in dm-raid1 & dm-log, do *not* use these patches now if you are using mirror (raid1) target !=20 (Remaining patches - including raid1 - are waiting in Alasdair's mail...) Milan -- mbroz@redhat.com > Le 27 sept. 06 =E0 12:36, Milan Broz a =E9crit : >=20 >> 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 >> >> --=20 >> mbroz@redhat.com >> >> The MoonSeeker napsal(a): >>> Yes I really need it. I have to create a virtual network editor for m= y >>> diploma project. So I have found many virtual solutions but the beste= st >>> 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 ba= sed >>> 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 =E0 23:14, Jan Blunck a =E9crit : >>> >>>> 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=E9moi= re >>>>> 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 sing= le >>>> 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?