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] [Solved] Using xm block-{attach,detach}

To: dbareiro@xxxxxxx
Subject: Re: [Xen-users] [Solved] Using xm block-{attach,detach}
From: "trilok nuwal" <tc.nuwal@xxxxxxxxx>
Date: Fri, 6 Apr 2007 10:38:23 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 05 Apr 2007 22:07:18 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=LehpJ/3uYgmAL3CNzSqDTfcg6yOm9oQhvPXhJAu/JAIUubngZGv5wVYLHt10F+F3AbdoXsEDwL5NtRgt7AtOmEWmXQz8LR4FhLf1TELsx0V7N6N1zVkHPXIJcvDBfLsnesHZnEH7dWAJ9g32n5/pjGljlNMpA2PrAC1h5eZVs1I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=dAqmygg7f0uUhFhAlKi7MXGHfEvHdqTCzxrG+tMRkFqSD8wyity8pMQGgcMa7msldGWtdtDWVKUBEOoMEapD/MYTPyTUwtSwieeuTVG/DkO+VXs/TCbmjWjfh/5NCKID80G6ssXEQpjEARN2yAPdZwyU8PVGmn/TpmglSQTL6b4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070406013903.GA6846@xxxxxxxxxxxxxxxxxxxxxxx>
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: <20070403011707.GA17815@xxxxxxxxxxxxxxxxxxxxxxx> <f58fc26d0704030118o7b2d6ab4oe124b8f8ba0e611@xxxxxxxxxxxxxx> <20070403191553.GA22857@xxxxxxxxxxxxxxxxxxxxxxx> <f58fc26d0704032213m4771e874nc8e9d62d17e82b19@xxxxxxxxxxxxxx> <20070404183039.GA26581@xxxxxxxxxxxxxxxxxxxxxxx> <f58fc26d0704042145y1c6327b0i62e284a926c9388b@xxxxxxxxxxxxxx> <20070405133420.GA29728@xxxxxxxxxxxxxxxxxxxxxxx> <f58fc26d0704050647v535ca94doaf72018c1ed16862@xxxxxxxxxxxxxx> <20070405173535.GA30054@xxxxxxxxxxxxxxxxxxxxxxx> <20070406013903.GA6846@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Ok, Actually i am using the RHEL distribution. Where i dont need to create the node explictly as yours case it is requird.

Thanks,
Trilok

On 4/6/07, Daniel Bareiro <daniel-listas@xxxxxxx> wrote:
On Thursday, 05 April 2007 14:35:35 -0300,
Daniel Bareiro wrote:

> I've successfully formatted the LVM backed-vbd on dom0. Then I attach
> it to domU. Both cat /proc/partitions and hwinfo reports the new
> exported LV backed-vbd, but I can't operate on it:

> ws1:/proc# cat /proc/partitions
> major minor  #blocks  name

>    3     3   31457280 hda3
>    3     2    5242880 hda2
>    3     1     262144 hda1
>    3     4    5242880 hda4

> ws1:/proc# mount /dev/hda4 /mnt/
> mount: you must specify the filesystem type
> ws1:/proc# mount -t reiserfs /dev/hda4 /mnt/
> mount: special device /dev/hda4 does not exist

I made the block special file and then I can access to the exported
lvm-backed vbd inside the domU:

ws1:~# mknod -m 660 /dev/hda4 b 3 4
ws1:~# mount /dev/hda4 /mnt/
ws1:~# df -h
S.ficheros          Tamaño Usado  Disp Uso% Montado en
/dev/hda2             5,0G  358M  4,7G   7% /
/dev/hda3              30G   22G  8,8G  71% /home/mirror
/dev/hda4             5,0G   33M  5,0G   1% /mnt

Thanks for all your replys.

Regards,
Daniel
--
Daniel Bareiro - System Administrator
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Etch - Linux user #188.598

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGFaS3Zpa/GxTmHTcRAscjAKCDAUu3vp/+LLWq8lsrRBsprFDFRwCdFqnm
MBdaLXMhD0hm3mKzoP3z2Cc=
=i1QD
-----END PGP SIGNATURE-----

_______________________________________________
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