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] Changing the size of an exported block device

To: Andy Smith <andy@xxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Changing the size of an exported block device
From: Kris Buytaert <mlkb@xxxxxxxxx>
Date: Thu, 26 Jan 2006 16:48:22 +0100
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 26 Jan 2006 15:57:37 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060126143440.GV7017@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20060126143440.GV7017@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2006-01-26 at 14:34 +0000, Andy Smith wrote:
> Hello,
> 
> Say I have an LVM LV exported to a running domU, and I want to
> increase the size of that LV.  I can lvextend from dom0, and I can
> use whatever filesystem tools I like to extend that fs in dom0 if I
> were to mount it.
> 
> However I understand that if the domU were to try to write beyond
> the end of the block device's limits as it knew when it was exported
> then it will get very upset.
> 
> What is the correct procedure in this circumstance?  Is it possible
> to withdraw the block device from the domU and then export it again
> so that it sees it as new?
> 

Assuming that is not your root filesystem you want to withraw from a
domU 
The commmands below should solve your problem.

Virtual Device Commands:
block-attach <DomId> <BackDev> <FrontDev> <Mode>
                [BackDomId]         Create a new virtual block device
   block-detach  <DomId> <DevId>    Destroy a domain's virtual block
device,
                                    where <DevId> may either be the
device ID
                                    or the device name as mounted in the
guest
   block-list <DomId>               List virtual block devices for a
domain

> Thanks,
> Andy
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
-- 
Kris Buytaert <mlkb@xxxxxxxxx>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>