I am expecting to have lots of (up to million) scattered extents across some volumes which I am required to mirror. Since mirror mapped device with a table that large consume unbearable amount of memory (e.g. for 10,000 extents I saw about 6 Giga of memory allocated by the device-mapper) I am going to create two linear devices which maps these extents and mirror them. In addition, I am required to preserve the original extent's offsets since they are an existing user data used by DB applications. To achieve that I will create another linear device to simulate the original extent's offsets which shall be mapped to the created mirrored device so, the client will continue to read and write the same offsets. -----Original Message----- From: Alasdair G Kergon [mailto:agk@xxxxxxxxxx] Sent: Tuesday, March 01, 2011 3:46 PM To: Eli Malul Cc: dm-devel@xxxxxxxxxx Subject: Re: Huge memory allocation On Tue, Mar 01, 2011 at 03:04:56PM +0200, Eli Malul wrote: > dm_malloc_aux do not allow memory allocation greater than 50000000. That was to catch software bugs: it was a number bigger than ever needed. Change it if you need to, but I need stronger evidence of the need for your particular way of doing things before I'll change it in the upstream tree! Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
