- Original Message -
From: Eli Mesika emes...@redhat.com
To: Dead Horse deadhorseconsult...@gmail.com
Cc: users@ovirt.org
Sent: Sunday, July 22, 2012 10:46:48 AM
Subject: Re: [Users] ovirt-engine upgrade 3.0 to 3.1 issue
- Original Message -
From: Dead Horse
On 07/20/2012 09:19 PM, Trey Dockendorf wrote:
On Fri, Jul 20, 2012 at 11:32 AM, Itamar Heim ih...@redhat.com wrote:
On 07/20/2012 07:21 PM, Trey Dockendorf wrote:
On Fri, Jul 20, 2012 at 3:52 AM, Itamar Heim ih...@redhat.com wrote:
On 07/20/2012 02:08 AM, Trey Dockendorf wrote:
On Thu,
Sounds like a good candidate for engine_3.1 gerrit branch (after push to
master), and probably a release blocker as well.
- Original Message -
- Original Message -
From: Eli Mesika emes...@redhat.com
To: Dead Horse deadhorseconsult...@gmail.com
Cc: users@ovirt.org
- Original Message -
On 07/20/2012 09:19 PM, Trey Dockendorf wrote:
On Fri, Jul 20, 2012 at 11:32 AM, Itamar Heim ih...@redhat.com
wrote:
On 07/20/2012 07:21 PM, Trey Dockendorf wrote:
On Fri, Jul 20, 2012 at 3:52 AM, Itamar Heim ih...@redhat.com
wrote:
On 07/20/2012
On 2012-7-22 19:51, Ayal Baron wrote:
- Original Message -
On 07/20/2012 09:19 PM, Trey Dockendorf wrote:
On Fri, Jul 20, 2012 at 11:32 AM, Itamar Heim ih...@redhat.com
wrote:
On 07/20/2012 07:21 PM, Trey Dockendorf wrote:
On Fri, Jul 20, 2012 at 3:52 AM, Itamar Heim
SNIP
Would a qcow2 image with preallocation=metadata be possible on an
iSCSI data store?
ayal?
nope. metadata preallocation means that each logical block has a
corresponding physical block.
Ayal, by saying logical block and physical block here, what do
they
stand for in linux
6 matches
Mail list logo