Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-15 Thread Nir Soffer
On Tue, Mar 15, 2016 at 1:14 PM, Pavel Gashev wrote: > Nir, > > > On 05/03/16 15:35, "Nir Soffer" wrote: >>On Sat, Mar 5, 2016 at 10:52 AM, Pavel Gashev wrote: >>> On 05/03/16 02:23, "Nir Soffer" wrote: On Sat, Mar 5, 2016 at 12:19 AM, Pavel Gashev wrote: > Also please consider qcow co

Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-15 Thread Pavel Gashev
Nir, On 05/03/16 15:35, "Nir Soffer" wrote: >On Sat, Mar 5, 2016 at 10:52 AM, Pavel Gashev wrote: >> On 05/03/16 02:23, "Nir Soffer" wrote: >>>On Sat, Mar 5, 2016 at 12:19 AM, Pavel Gashev wrote: Also please consider qcow compat=1.1 as default disk format both for file and block st

Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-07 Thread Nicolás
rwise the workaround works perfectly. Thanks. Mensaje original De: Nir Soffer Fecha:04/03/2016 23:23 (GMT+00:00) Para: Pavel Gashev Cc: Nicolás ,amureini ,users@ovirt.org Asunto: Re: [ovirt-users] Storage migration: Preallocation forced on destination On Sat, Mar 5, 20

Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-05 Thread Nir Soffer
On Sat, Mar 5, 2016 at 10:52 AM, Pavel Gashev wrote: > On 05/03/16 02:23, "Nir Soffer" wrote: > >>On Sat, Mar 5, 2016 at 12:19 AM, Pavel Gashev wrote: >>> I think it's hard to calculate the additional space for cow format without >>> analysing raw image. It's better to allocate enough space, an

Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-05 Thread Pavel Gashev
On 05/03/16 02:23, "Nir Soffer" wrote: >On Sat, Mar 5, 2016 at 12:19 AM, Pavel Gashev wrote: >> I think it's hard to calculate the additional space for cow format without >> analysing raw image. It's better to allocate enough space, and then decrease >> it after qemu-img convert. > >We use 10%

Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-04 Thread Nicolás
El 04/03/16 a las 20:23, Nir Soffer escribió: On Fri, Mar 4, 2016 at 7:07 PM, Nicolás wrote: Hi, We're migrating an existing storage (glusterfs) to a new one (iSCSI). All disks on glusterfs are thin provisioned, but when migrating to iSCSI the following warning is shown: The following di

Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-04 Thread Nir Soffer
On Sat, Mar 5, 2016 at 12:19 AM, Pavel Gashev wrote: > I think it's hard to calculate the additional space for cow format without > analysing raw image. It's better to allocate enough space, and then decrease > it after qemu-img convert. We use 10% as a rough estimate for additional space when

Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-04 Thread Pavel Gashev
I think it's hard to calculate the additional space for cow format without analysing raw image. It's better to allocate enough space, and then decrease it after qemu-img convert. Please note that while disk moving keeps disk format, disk copying changes format. So when you copy a thin provision

Re: [ovirt-users] Storage migration: Preallocation forced on destination

2016-03-04 Thread Nir Soffer
On Fri, Mar 4, 2016 at 7:07 PM, Nicolás wrote: > Hi, > > We're migrating an existing storage (glusterfs) to a new one (iSCSI). All > disks on glusterfs are thin provisioned, but when migrating to iSCSI the > following warning is shown: > > The following disks will become preallocated, and may

[ovirt-users] Storage migration: Preallocation forced on destination

2016-03-04 Thread Nicolás
Hi, We're migrating an existing storage (glusterfs) to a new one (iSCSI). All disks on glusterfs are thin provisioned, but when migrating to iSCSI the following warning is shown: The following disks will become preallocated, and may consume considerably more space on the target: local-di