One way to achieve that is to create two linear mapped devices amd mirror them and another two linear device to simulate the original offsets. The last shall be mapped to the first two linear devices so the client will continue to read and write the same offsets he was used to. Seems a little bit complex configuration but it shall do the trick. I will test its scalability and update of course. BTW - CONFIG_BLK_DEV_INTEGRITY is disabled. -----Original Message----- From: Eli Malul Sent: Monday, February 28, 2011 3:43 PM To: 'Alasdair G Kergon' Cc: device-mapper development Subject: RE: mirrored device with thousand of mappingtableentries According to your suggestion I need to map the non contiguous extents into linear devices and mirror them. But, what if I am required to preserve the original extent's offset? Since I need to mirror an existing device with user data already on it... -----Original Message----- From: Alasdair G Kergon [mailto:agk@xxxxxxxxxx] Sent: Monday, February 28, 2011 3:29 PM To: Eli Malul Cc: device-mapper development Subject: Re: mirrored device with thousand of mappingtableentries On Mon, Feb 28, 2011 at 03:13:42PM +0200, Eli Malul wrote: > But, do you know why having 10,000 extents is causing this overwhelming > memory usage? Nobody considered having a huge number of tiny mirrors reasonable or necessary so no attempt has been made to optimise that situation. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
