Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQ4lF-00005O-Ul for qemu-devel@nongnu.org; Thu, 22 Jan 2009 13:58:42 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQ4lE-0008VG-Vp for qemu-devel@nongnu.org; Thu, 22 Jan 2009 13:58:41 -0500 Received: from [199.232.76.173] (port=46451 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQ4lE-0008V1-P9 for qemu-devel@nongnu.org; Thu, 22 Jan 2009 13:58:40 -0500 Received: from e35.co.us.ibm.com ([32.97.110.153]:33882) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LQ4lE-0002Yu-9q for qemu-devel@nongnu.org; Thu, 22 Jan 2009 13:58:40 -0500 Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e35.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id n0MItqFF031902 for ; Thu, 22 Jan 2009 11:55:52 -0700 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id n0MIwS4h189486 for ; Thu, 22 Jan 2009 11:58:35 -0700 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n0MIwONq007640 for ; Thu, 22 Jan 2009 11:58:24 -0700 Message-ID: <4978C1C4.8080709@us.ibm.com> Date: Thu, 22 Jan 2009 12:58:12 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/5 v2] qcow2 info: show highest-allocation and num-free-bytes References: <1232621035-4951-1-git-send-email-uril@redhat.com> In-Reply-To: <1232621035-4951-1-git-send-email-uril@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Uri Lublin Uri Lublin wrote: > Hello, > > The following 5 enhance "info blockstats" for qcow2 images (and > other formats that implement bdrv_get_info), to show > higest-allocated-offset and number-of-free-bytes (below > the higest-allocated-offset) of the image. > > One of the main usage for this information is to know and act > upon a case of end-of-storage-space. Instead of waiting for > -ENOSPACE (which now may cause the VM to stop), one can > define a threshold and extend the diskspace allocated for > the image. > This info is also good for management systems, so they > can report the user disk space status. > > Also with highest_alloc and num_free_bytes, we can have a pretty > good idea about how fragmented a qcow2 images is, and try to > defragment it later. > > Patches 1,2,3, Provides information about the highest allocated byte (offset) > Patch 4, Provides information about the number of free bytes > below highest_alloc. > Patch 5, Provides info about highest_alloc and num_free_bytes through > qemu-img info > > > Changes from v1: better description of use cases. > Applied all. Thanks. Regards, Anthony Liguori > Regards, > Uri. > > > >