Re: [Xen-users] Physical to Virtual Migration

[James Miller <jimm@xxxxxxxxxxxxxxx>]

Fajar A. Nugraha wrote:
> On Thu, Jan 29, 2009 at 3:58 AM, James Miller <jimm@xxxxxxxxxxxxxxx> wrote:
>   
> > I'm having an issue migrating an OLD debian 3.0 linux server (2.4.18 kernel)
> >     
> Ouch!
>
>   
> > to an HVM domU.  I'm using Xen 3.3.0 compiled from source.
> > Here's the process I took:
> > 1. Carve out a chunk of space from an LVM Volume group
> > 2. Create and boot from a Debian live CD ISO
> > 3. Fdisked the LV into 2 partitions /dev/hda1 (OS)  /dev//hda2 (SWAP)
> > 4. Formatted /dev/hda1 as ext3 and /dev/hda2 (swap)
> >     
> So you're using mkfs.ext from a new Debian live CD?
>
>   
> > When I reboot I get the following errors about reisersf -- which makes no
> > sense considering I'm using ext2/ext3:
> > EXT3-fs unsupported inod size: 256
> >     
> This might be problem : inode size
>
>   
> > read_super_block: can't find a reiserfs filesytem on (dev 03:01, block 64,
> > size 1024)
> >     
> I think this line simply means you have reiserfs built into the
> kernel, and the kernel tried to mount root as reiserfs, which
> obviously will fail.
>
>   
> >  But I am wondering if it has anything to do with OLD e2fs tools..
> >     
> It should be. From mkfs.ext3 man page :
>
>        -I inode-size
>               Specify the size of each inode in bytes.  mke2fs creates
> 256-byte inodes by default.  In kernels after 2.6.10 and some earlier
> vendor kernels it  is
>               possible  to  utilize inodes larger than 128 bytes to
> store extended attributes for improved performance.  The inode-size
> value must be a power of 2
>               larger or equal to 128.  The larger the inode-size the
> more space the inode table will consume, and this reduces the usable
> space in the  filesystem
>               and  can  also  negatively  impact performance.
> Extended attributes stored in large inodes are not visible with older
> kernels, and such filesystems
>               will not be mountable with 2.4 kernels at all.  It is
> not possible to change this value after the filesystem is created.
>
> you may try reformatting with -I 128, or (a safer choice) use
> mkfs.ext3 from your old Debian 3.0 backup
>
> Regards,
>
> Fajar
>
>   
Thank you for the suggestion Fajar.  I used mkfs.ext2 (just bypassed 
ext3 all together =) from the old, physical, sever and all is good.

--Jim




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