[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-users] Re: Multi-partition domain not recognizing extra partitions
- To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
- From: Antoine Benkemoun <antoine.benkemoun@xxxxxxxxx>
- Date: Fri, 28 May 2010 12:28:54 +0200
- Delivery-date: Fri, 28 May 2010 03:44:31 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=JF5EZ0iVL6w1c0GRsaPhNEpsdaegHn+tP4jvq0qdAyMt+LSxevx8cEnSAxZSd1ze7M +eZwdQw40sV8Ayl1N2Sh22nDpbat3nly51ZfqowYHHUYYiJ63SriFEajjq/igX1tqNMg kUgIJfQXRYnPGAjTQop14wG3WGM06m/hNdjqc=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Solved !
Needed udev...
On Fri, May 28, 2010 at 11:55 AM, Antoine Benkemoun <antoine.benkemoun@xxxxxxxxx> wrote:
Hello,
I have been having an annoying problem with a multi-partition domain. This domain has a separate partition for : /, /home, /usr, /var, /tmp and /data. I created it using xen-tools and the custom partitionning scheme option. The partitions are inside a LVM.
When I boot the domain, it mounts the / and swap partition but none of the others. Therefore it doesn't work... I get the following error :
fsck.ext3: No such file or directory while trying to open /dev/xvda6
/dev/xvda6:
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>
When I mount the partitions in question in the dom0, it works perfectly fine. When I fsck.ext3 the partitions in question, it returns no errors.
In the dmesg I get the following messages, I don't know if they're relevant.
[ 0.187583] blkfront: xvda7: barriers enabled
[ 0.189567] blkfront: xvda6: barriers enabled
I also see this message that seems to correspond to the partitions :
[ 0.045069] xenbus_probe_devices device
[ 0.045069] xenbus_probe_devices 1/3 vbd
[ 0.045069] xenbus_probe_device_type type vbd
[ 0.045069] xenbus_probe_device_type 1/7 51719
[ 0.045069] xenbus_probe_device_type 2/7 51718
[ 0.046084] xenbus_probe_device_type 3/7 51717
[ 0.046084] xenbus_probe_device_type 4/7 51716
[ 0.046084] xenbus_probe_device_type 5/7 51715
[ 0.046084] xenbus_probe_device_type 6/7 51714
[ 0.046084] xenbus_probe_device_type 7/7 51713
My domU configuration is the following :
root = '/dev/xvda2 ro'
disk = [
'phy:/dev/vg/test-home,xvda7,w',
'phy:/dev/vg/test-data,xvda6,w',
'phy:/dev/vg/test-tmp,xvda5,w',
'phy:/dev/vg/test-usr,xvda4,w',
'phy:/dev/vg/test-var,xvda3,w',
'phy:/dev/vg/test-root,xvda2,w',
'phy:/dev/vg/test-swap,xvda1,w',
]
What have I done wrong ? I have tried many things... DomU is a fresh Debian Lenny and the partitions are ext3. dom0 is also Debian Lenny. Xen is version 4.0 compiled from source. I tried with XFS but I got the same error.
Thank you in advance for your help,
Antoine
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
