<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
resending ack<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject: </th>
<td>Re: [Ovirt-devel] [PATCH 1/2] Provides a new storage
administration system to the managed node.</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
<td>Mon, 09 Nov 2009 15:22:56 -0500</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
<td>Joey Boggs <a class="moz-txt-link-rfc2396E" href="mailto:jboggs@redhat.com"><jboggs@redhat.com></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
<td>Darryl L. Pierce <a class="moz-txt-link-rfc2396E" href="mailto:dpierce@redhat.com"><dpierce@redhat.com></a>,
<a class="moz-txt-link-abbreviated" href="mailto:ovirt-devel@redhat.com">ovirt-devel@redhat.com</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>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
<a class="moz-txt-link-abbreviated" href="mailto:Ovirt-devel@redhat.com">Ovirt-devel@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/ovirt-devel">https://www.redhat.com/mailman/listinfo/ovirt-devel</a>
</pre>
</body>
</html>