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

Re: [Xen-users] real HDD usage of XEN images


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Heiko <rupertt@xxxxxxxxx>
  • Date: Thu, 15 Jan 2009 15:55:58 +0100
  • Delivery-date: Thu, 15 Jan 2009 06:56:40 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=eHmB8cJPHLp0kij9hVIhbwDFpZcUzPdJp5WWnnfQYTNma8TJB9P6uJW2UxJakZFVPk ubqCrIu5qVHT4bD1fbmYD0fAySB83devL434dBXyU26dUZtMkXJytgJiY4TVDNlmI40O axvZ4wXnWmG5dL9/F6emHO2T06oOb1tadNL0E=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Thu, Jan 15, 2009 at 3:31 PM, Kai Schaetzl <maillists@xxxxxxxxxxxxx> wrote:
> Heiko wrote on Thu, 15 Jan 2009 14:42:46 +0100:
>
> I think you are confusing df/du/ls soemtimes. You give figures that you say
> are from df, but later it turns out they are from ls etc. Try to be more
> precise in what you tell and what you do.
>
>> [root@x1blade1:/VM]# df -h
>
> the df in your first mail was from a different host. Just confusing you *and*
> me.
true, sorry. but I found this to be a better example.

>
>> [root@x1blade1:/VM]# ls -lah
>> total 50G
>> drwxr-xr-x  2 root root 4.0K Jan 15 11:24 .
>> drwxr-xr-x 25 root root 4.0K Mar 10  2008 ..
>> 2.0G May  5  2008 auto-input_swapfile.img
>> 31G Jan 15 13:36 auto-input-vm1.img
>> 2.0G Mar 13  2008 distribution_swap.img
>> 11G Jan 15 13:36 distribution-vm1.img
>> 26G Jan 15 13:36 monitoring-1.img
>> 2.0G Mar 19  2008 monitoring-1_swapfile.img
>> 2.0G Jan  7 08:26 translator_swap.img
>> 11G Jan 15 13:36 translator-vm1.img
>> 11G Jan 15 13:36 uat-vm1.img
>> 2.0G Mar 26  2008 uat-vm1_swapfile.img
>
> I told you to use "du -s *" in that directory, I don't think you did that. If
> you would you would get figures from the individual files that are *not* the
> same as above! (Or if you want human-readable format, use "du -sh *".)
>
[root@x1blade1:/VM]# du -s
52085392

I just pasted the above lines to show what I mean by difference
between the two statements.


> Obviously the file sizes above add up to more than 50 GB. Which means there
> *are* sparse files in use. (*) I don't know where "ls" gets the "total" from,
> but that's obviously the actually committed total in reserved blocks = the
> size that is actually in use. The size for the individual files is *not* the
> size in use, but what is stored somewhere (inode, whereever, I'm not an fs

> expert) as the given size at creation time. If it is a sparse file this shows
> the size value it can grow to. It does not show the actual size on the file
> system (that is what du is for, and df != du)
>
thats the thing i wanted to find out

> (*)Overcommitting in such a way is actually dangerous. I think that should be
> obvious.
>
of course. leaves me with some missing space, where to put the VM that
are to much now.

Thx for the info and sorry for any confussion.



> Kai
>
> --
> Kai SchÃtzl, Berlin, Germany
> Get your web at Conactive Internet Services: http://www.conactive.com
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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