[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] A question of Virtual Disk(VHD) size in thin provisioning NFS SR

  • To: xen-api@xxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Tue, 22 Jan 2013 13:34:37 +0400
  • Delivery-date: Tue, 22 Jan 2013 09:34:51 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

difference between disk size in OS (blockdev --getsize64 /dev/xvda) and VHD size is thin provision stuff.

difference between du and caused by holes in file (sparce file).

Please note, that VDI can consists from few VHD files (so called VHD tree). That usually happens with cross-pool migration, snapshots and vm clonning.

22.01.2013 07:15, ND KK пишет:
Hello all, 
I have a question. But my English is very poor, I hope you will understand

My VM has one virtual disk which allocated 100G 

I find the utilization of this disk in guest OS is 39.5G ( Get utilization on guest OS file system)

but  I ssh to the NFS server check the VHD files size
I use command: ls -lh  VHD_FILE_NAME ( Get utilization on NFS server file system)
It show that 
-rw-r--r-- 1 root root 19G Jan 22  2013 XXXXXXX.vhd

Then, I use command: du -sh VHD_FILE_NAME ( Get physical utilization on disk )
It show that 
5.5G  XXXXXXXX.vhd

My question is what happen in this process ( 100G -> 39.5G -> 19G -> 5.5G )

Are they representing  XenServer's thin provision, VHD's thin provision and File System sparse file ?

Does XenServer's thin provision equals VHD's thin provision? VHD's thin provision equals File System sparse file ?

If yes,  what happen in this process?


Best Regards,
Leo Hsu

Xen-api mailing list

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.