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

Re: [Xen-users] Resize DomU partition


  • To: Ian Tobin <itobin@xxxxxxxxxxxxx>
  • From: KC LO <kclo2000@xxxxxxxxx>
  • Date: Tue, 2 Mar 2010 21:01:33 +0800
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 02 Mar 2010 05:02:36 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wXc0XSN6jjARUf9bxcK7YdUcFfJJ4RSvv0Nr6eWj0qTlFvweenQLwpHulbQaKnaT7H 1pKcLq/+A6Y2UDw9h2KTNUzRBuEw8JlTz7Xk/QFx1lH9OHntAnXfxduG1gPAveqx9WIh 0B2+Rc3hRfGWpYrXODbSFI1R/InsJIsJxs9+o=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi ,

Thanks for your reply!
However, I got the following errors on the first command

e2fsck 1.39 (29-May-2006)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/VolGroup00/vm3

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

I guess that the file system is ext3 which got this problem.  Any hints?

On 2 March 2010 06:25, Ian Tobin <itobin@xxxxxxxxxxxxx> wrote:
> Hi,
>
> Shutdown DomU
>
> e2fsck -f /dev/VolGroup00/vm1
> resize2fs /dev/VolGroup00/vm1
> fsck -n /dev/VolGroup00/vm1
>
>
> boot DomU and that should do it.  Resize2fs should automatically use all
> available space, if not you will need to add the parameter.
>
> Ian
>
>
>
>
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of KC LO
> Sent: 01 March 2010 22:17
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Resize DomU partition
>
> Hi all,
>
> I have created a DomU guest based on the following method :-
> 1) I create a LV with size 6GB : lvcreate -L 6G
> 2) I setup a new guest DomU with /dev/VolGroup00/vm1 as disk device
> 3) In DomU, I use /dev/hda as device to create partition for /boot, /,
> and swap without using LVM
>  fdisk -l /dev/hda
>
> Disk /dev/hda: 10.7 GB, 10737418240 bytes
> 255 heads, 63 sectors/track, 1305 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>   Device Boot      Start         End      Blocks   Id  System
> /dev/hda1   *           1          13      104391   83  Linux
> /dev/hda2              14         521     4080510   83  Linux
> /dev/hda3             522         782     2096482+  82  Linux swap /
> Solaris
>
> 4) I am now resize the /dev/VolGroup00/vm1 device to 10G in Dom0
> lvextend -L 10g dev/VolGroup00/vm1
>
> How can DomU to recongnize the new disk space?
>
> Thanks!
>
> _______________________________________________
> 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®.