From: Timo Benk <timo.benk@gmx.de>
To: Xen Devel <xen-devel@lists.xensource.com>
Subject: Re: RE: 3.0.3rc2 BUG: LVM backed qcow image not working?
Date: Thu, 12 Oct 2006 20:34:30 +0200 [thread overview]
Message-ID: <452E8AB6.10200@gmx.de> (raw)
In-Reply-To: <452E8A4A.7030705@gmx.de>
Thats also interesting ...
xendom0:~ # ps -ef | grep mount
Segmentation fault
Timo Benk wrote:
> Next try,
>
> using a logical partition ...
>
> === prepare image partition ===
> # mkreiserfs /dev/hdc5
> # mount /dev/hdc5 /var/lib/xen/images
>
> === prepare base partition ===
> # mkreiserfs /dev/hdc6
> # mount /dev/hdc6 /mnt
> # tar cpjf domu-base.tar.bz2 -C /mnt
>
> === create file backed qcow image ===
> # qcow-create 5120 /var/lib/xen/images/xengate_root.qcow
> /dev/hdc6
> # xm block-attach Domain-0
> tap:qcow:/var/lib/xen/images/xengate_root.qcow xvda1 w 0
> # mount /dev/xvda1 /mnt
> [... changing some files ...]
>
> # umount /mnt
> [... umount is hanging forever ...]
>
> # dmesg
> [... nothing interesting ...]
>
> Do i anything wrong here? Or maybe a broblem with reiserfs?
>
> BTW, how stable is qcow considered at the moment? Reading the README
> it seams quite mature to me.
>
> Greetings,
> -timo
>
> Timo Benk wrote:
>> Hi,
>>
>> Sorry, small typo ...
>>
>> i try to create a LVM backed qcow image, but it seems qcow does not
>> like LVM.
>>
>> === create qcow image LV ===
>> # lvcreate --name xendom_qcow --size 100G xenvol
>> # mkreiserfs /dev/xenvol/xendom_qcow
>> # mount /dev/xenvol/xendom_qcow /var/lib/xen/images
>>
>> === create base LV and fill with data ===
>> # lvcreate --name xendom_base_qcow --size 10G xenvol
>> # mkreiserfs /dev/xenvol/xendom_base_qcow
>> # mount /dev/xenvol/xendom_base_qcow /mnt
>> # tar cpjf domu-base.tar.bz2 -C /mnt
>>
>> === create file backed qcow image ===
>> # qcow-create 5120 /var/lib/xen/images/xengate_root.qcow
>> /dev/xenvol/xendom_base_qcow
>> # xm block-attach Domain-0
>> tap:qcow:/var/lib/xen/images/xengate_root.qcow xvda1 w 0
>> # mount /dev/xvda1 /mnt
>> [... mount is hanging forever ...]
>>
>> # dmesg
>> [...]
>> ReiserFS: xvda1: checking transaction log (xvda1)
>> blk_tap: Can't get UE info
>>
>> ???
>>
>> Greetings,
>> -timo
>>
>
>
--
Timo Benk - Jabber ID: fry@jabber.org - ICQ ID: #241877854
PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc
prev parent reply other threads:[~2006-10-12 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 17:55 3.0.3rc2 BUG: LVM backed qcow image not working? Timo Benk
2006-10-12 18:32 ` Timo Benk
2006-10-12 18:34 ` Timo Benk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=452E8AB6.10200@gmx.de \
--to=timo.benk@gmx.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.