WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: RE: how to expand a xen image?

To: "henry ritzlmayr" <xen-list@xxxxxx>
Subject: Re: [Xen-users] Re: RE: how to expand a xen image?
From: Heiko <rupertt@xxxxxxxxx>
Date: Wed, 3 Sep 2008 16:42:13 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 03 Sep 2008 07:42:56 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=dBWVPaQrBXE/vEmzbpjAhYO66I1wCT/qXe6kptvH+3E=; b=KRQtrqFYcPSruuPjA56JccIHhRKSlYCnCOqTOe1EV6jmxVcZmSatH06YgvqFzWTYOb wUcuWNWxo1ZlH/RSmQ3q1B72SMOyCVjM5ksz8rVp0D71UPurSaW8kOXRUat/6qzwiCu2 jd1w9rVyjmBPZDAjY8DEcL/xOug/LtU6fDcTQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=JBvMzrQUM689xEapm/Nr3fH1Z16yADMa/Qhy0IDEkkRd/xf/n2wu2GW7tcvtQRJAdj 2IoZHjI1SncwSOya1dabo+221awnRdo72gFMjHNgf5S/NT0jDnbfR7TOD2QolzTYmBP0 psSDXk+NllQPbWdP5Ge7vfw6+9f6xhSADfI9w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1220427531.3139.17.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <48BD44AD.8080909@xxxxxxxxxxxxxx> <1220366296.1930.19.camel@xxxxxxxxxxxxxxxxxxxxx> <157.894826452498$1220368488@xxxxxxxxxxxxxx> <1220421478.3139.3.camel@xxxxxxxxxxxxxxxxxxxxxx> <537dcd6b0809022341le1f235cud9c8023dc4c986c7@xxxxxxxxxxxxxx> <1220427531.3139.17.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Sep 3, 2008 at 9:38 AM, henry ritzlmayr <xen-list@xxxxxx> wrote:
> Am Mittwoch, den 03.09.2008, 08:41 +0200 schrieb Heiko:
>> On Wed, Sep 3, 2008 at 7:57 AM, henry ritzlmayr <xen-list@xxxxxx> wrote:
>> > Am Dienstag, den 02.09.2008, 11:12 -0400 schrieb Dustin Henning:
>> >>       I'm not especially familiar with dd, but couldn't it be used for
>> >> this?  It seems I recall something about skipping blocks before writing, 
>> >> so
>> >> if you skip enough blocks to go to the end of the file and then write 
>> >> enough
>> >> blocks to extend it as much as you want, wouldn't this make the single 
>> >> disk
>> >> that much bigger the next time it is mounted to a domU?  Obviously it 
>> >> would
>> >> be wise to back-up the image first, and this would probably be an offline
>> >> operation, but it seems to me it might be better (or at least easier to
>> >> manage) than having two physical volumes (unless you want to use two real
>> >> disks or something).
>> >>       Dustin
>> >
>> > If you like it within one file:
>> >
>> > dd if=/dev/zero bs=1G count=5 >> imagefile
>> >
>> > adds five gigs to your imagefile.
>> >
>> Hello,
>>
>> I did it a couple of time the following way:
>>
>> shut down the VM,
>>
>> dd if=/dev/zero of=/VM/myxen_back_grow.img bs=1M conv=notrunc
>> count=5000 seek=10240
>> count is the size that you wanna add(here 5GB more)
>
> If you do it that way, be careful on the seek parameter. It has to be at
> least bigger than the original file and for performance reasons (sparse
> file) it should exactly match the file size.
>
> That´t why I prefer it the way I posted it above which does the same
> thing but avoiding both problems.
>
sounds and looks much better, thx for that advice, i did put it into
my documentation.

cheers

Rupert
> Henry
>
>
>
> _______________________________________________
> 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