From: yuxh <yuxinghai@cn.fujitsu.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-img problem when create a file larger than fs's size
Date: Wed, 08 May 2013 15:34:07 +0800 [thread overview]
Message-ID: <5189FFEF.3080202@cn.fujitsu.com> (raw)
In-Reply-To: <20130508063656.GA2766@fam-laptop.nay.redhat.com>
Thank you for your reply. I agreed what you said.
And do you think we shall print a prompt to user when the size user
specified is larger than available space ?
On 05/08/2013 02:36 PM, Fam Zheng wrote:
> I think it's the system admin to be responsible for the risk of over
> provisioning. We have host sparse file[1] (as your example) for
> preallocated image (for example, -f raw), as well as sparse image (as
> supported in qcow2, vmdk, etc.). There are cases that host file system
> is extended or the vm disk is moved to a larger storage when the actual
> data grows closer to full, so it's not very practical to limit the
> creating size, just as this is quietly valid in linux, no matter how
> small your /tmp is.
>
> # df /tmp/ -h
> Filesystem Size Used Avail Use% Mounted on
> tmpfs 3.8G 14M 3.8G 1% /tmp
> # touch /tmp/a
> # truncate /tmp/a --size 10000T
> # ls -l /tmp/a
> -rw-rw-r--. 1 fam fam 10995116277760000 May 8 14:33 /tmp/a
>
> [1]: http://en.wikipedia.org/wiki/Sparse_file
>
> On Wed, 05/08 13:18, yuxh wrote:
>> Hello all,
>>
>> I have to consult you a qemu-img's problem.
>>
>> Is this reasonable to create a file which is larger than the
>> available size of the fs by qemu-img cmd ?
>>
>> When I use qemu-img create a file which is larger than the available
>> size of the fs, the creation is completed succesfully.
>>
>> However when I use this file in guest as a guest's disk, and write
>> beyond the size the host file can provides, the guest was paused by
>> qemu-kvm or libvirt and was in maybe a infinite circle where the
>> guest just can't be used except I detach the disk from guest or
>> destroy the guest.
>>
>> I read the qemu-img's code and found it just create the file as we
>> required and doesn't check if the size we specify is reasonable.But
>> this may let the guest in a risk of meeting the problem I describe
>> above.
>>
>> Exp:
>> [root@build mytest]# df -ah /mytest/
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/sdb2 2.0G 3.1M 1.9G 1% /mytest
>> [root@build mytest]# qemu-img create -f raw test.raw 3G
>> Formatting 'test.raw', fmt=raw size=3221225472
>> [root@build mytest]# ls -l test.raw
>> -rw-r--r--. 1 root root 3221225472 May 8 12:23 test.raw
>> [root@build mytest]#
>>
>> Thank you.
>>
>> Best Regards
>> Xinghai Yu
>>
>
--
以上
第一软件事业部 第一开发部 driver组 于星海
Best Regards
--------------------------------------------------
Yu Xinghai
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
No.6 Wenzhu Road, Nanjing, 210012, China
TEL: +86+25-86630566-8533
FUJITSU INTERNAL: 7998-8533
FAX: +86+25-83317685
MAIL: yuxinghai@cn.fujitsu.com
--------------------------------------------------
next prev parent reply other threads:[~2013-05-08 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 5:18 [Qemu-devel] qemu-img problem when create a file larger than fs's size yuxh
2013-05-08 6:36 ` Fam Zheng
2013-05-08 7:34 ` yuxh [this message]
2013-05-08 8:20 ` Fam Zheng
2013-05-08 8:36 ` yuxh
2013-05-09 7:44 ` Stefan Hajnoczi
2013-05-09 8:22 ` yuxh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5189FFEF.3080202@cn.fujitsu.com \
--to=yuxinghai@cn.fujitsu.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).