From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50516) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cVy73-00023x-Su for qemu-devel@nongnu.org; Tue, 24 Jan 2017 05:14:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cVy71-0002QL-8X for qemu-devel@nongnu.org; Tue, 24 Jan 2017 05:14:05 -0500 Received: from mailhub.sw.ru ([195.214.232.25]:9334 helo=relay.sw.ru) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cVy70-0002Pj-SR for qemu-devel@nongnu.org; Tue, 24 Jan 2017 05:14:03 -0500 References: <1482503344-6424-1-git-send-email-vsementsov@virtuozzo.com> <1482503344-6424-9-git-send-email-vsementsov@virtuozzo.com> <20170124075949.GD27126@lemon.Home> <22f99aae-0968-286f-186c-0eaefadbe649@virtuozzo.com> <20170124093643.GA14811@lemon.Home> From: Vladimir Sementsov-Ogievskiy Message-ID: Date: Tue, 24 Jan 2017 13:13:47 +0300 MIME-Version: 1.0 In-Reply-To: <20170124093643.GA14811@lemon.Home> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 08/21] backup: skip unallocated clusters for full mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, kwolf@redhat.com, mreitz@redhat.com, jsnow@redhat.com, den@openvz.org, stefanha@redhat.com, pbonzini@redhat.com, jcody@redhat.com 24.01.2017 12:36, Fam Zheng wrote: > On Tue, 01/24 12:18, Vladimir Sementsov-Ogievskiy wrote: >> 24.01.2017 10:59, Fam Zheng wrote: >>> On Fri, 12/23 17:28, Vladimir Sementsov-Ogievskiy wrote: >>>> diff --git a/tests/qemu-iotests/055 b/tests/qemu-iotests/055 >>>> index 1d3fd04..388b7b2 100755 >>>> --- a/tests/qemu-iotests/055 >>>> +++ b/tests/qemu-iotests/055 >>>> @@ -30,6 +30,7 @@ target_img = os.path.join(iotests.test_dir, 'target.img') >>>> blockdev_target_img = os.path.join(iotests.test_dir, 'blockdev-target.img') >>>> image_len = 64 * 1024 * 1024 # MB >>>> +pause_write = '3M' >>>> def setUpModule(): >>>> qemu_img('create', '-f', iotests.imgfmt, test_img, str(image_len)) >>>> @@ -39,6 +40,7 @@ def setUpModule(): >>>> qemu_io('-f', iotests.imgfmt, '-c', 'write -P0xd5 1M 32k', test_img) >>>> qemu_io('-f', iotests.imgfmt, '-c', 'write -P0xdc 32M 124k', test_img) >>>> qemu_io('-f', iotests.imgfmt, '-c', 'write -P0x33 67043328 64k', test_img) >>>> + qemu_io('-f', iotests.imgfmt, '-c', 'write -P0xdc 40M ' + pause_write, test_img) >>> What does this iotest change do? >> Without this backup block-job finishes before the next query to it from test >> and test fails. This is a wide problem I suffer of on the way of backup >> improvement and it should have better solution then adjusting amount of data >> being copied... > You can use blkdebug to pause I/O before querying the block job, or simply > throttle it down. > > Fam throttling down is not better I thing then just copying additional 3M, it is environment-dependent hack too. And we can't use throttling in all tests - throttling should be itself tested separately. In the other thread there was an idea to not delete block jobs on their finish, but maintain them in some 'finished' state. This will be great for the case and will be generic. -- Best regards, Vladimir