resending ack
-------- Original Message --------
Subject: Re: [Ovirt-devel] [PATCH 1/2] Provides a new storage
administration system to the managed node.
Date: Mon, 09 Nov 2009 15:22:56 -0500
From: Joey Boggs <[email protected]>
To: Darryl L. Pierce <[email protected]>, [email protected]
Darryl L. Pierce wrote:
On Mon, Nov 09, 2009 at 02:54:50PM -0500, Joey Boggs wrote:
ACK pending below comments:
For lvm -It creates a pool fine, when creating a volume its missing the
volume group name when running lvcreate
+-----+ An Exception Has Occurred +-----+
Couldn't create storage volume '1.img': 'internal error '/sbin/lvcreate
--name 1.img -L 1024K /tmp/lvm' exited with non-zero status 3 and signal
0
Volume group name expected (no slash) Run `lvcreate --help' for more
information.
Does the same thing happen with virt-manager when doing the same thing?
virt-manager works fine but here's what wrong
/sbin/lvcreate --name 1.img -L 1024K /tmp/lvm' exited with non-zero status 3
and signal 0
/tmp/lvm should be /dev/$poolname not the target path, if you run the command
manually and sub in the right path.
iscsi creates a pool fine but when you reach creating a volume it tells
you it's no implemented, any way to block this option for even being
available or alert the user ahead of time?
All the other options create pools/volumes fine
I'm not sure if there's an easy way to block it without forcing us to
have to do an upgrade later when it's implemented. When I first saw
that, I double checked virt-manager and it's doing the same thing,
giving an error that the iSCSI pool is not available. So at least in
that way we're consistent.
ok wfm
_______________________________________________
Ovirt-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/ovirt-devel
_______________________________________________
Ovirt-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/ovirt-devel
