[ovirt-users] Importing VM fails with "No space left on device"

2021-05-08 Thread j . velasco 
Hello List,
I am facing the following issue when I try to import a VM from a KVM host to my 
oVirt (4.4.5.11-1.el8).
The importing  I done throuth GUI using the option of KVM provider.

-- Log1:
# cat 
/var/log/vdsm/import-57f84423-56cb-4187-86e2-f4208348e1f5-20210507T124121.log
[0.0] preparing for copy
[0.0] Copying disk 1/1 to 
/rhev/data-center/mnt/blockSD/cc9fae8e-b714-44cf-9dac-3a83a15b0455/images/cb63ffc9-07ee-4323-9e8a-378be31ae3f7/e7e69cbc-47bf-4557-ae02-ca1c53c8423f
Traceback (most recent call last):
  File "/usr/libexec/vdsm/kvm2ovirt", line 23, in 
kvm2ovirt.main()
  File "/usr/lib/python3.6/site-packages/vdsm/kvm2ovirt.py", line 277, in main
handle_volume(con, diskno, src, dst, options)
  File "/usr/lib/python3.6/site-packages/vdsm/kvm2ovirt.py", line 228, in 
handle_volume
download_disk(sr, estimated_size, None, dst, options.bufsize)
  File "/usr/lib/python3.6/site-packages/vdsm/kvm2ovirt.py", line 169, in 
download_disk
op.run()
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/ops.py", 
line 57, in run
res = self._run()
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/ops.py", 
line 163, in _run
self._write_chunk(count)
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/ops.py", 
line 188, in _write_chunk
n = self._dst.write(v)
  File 
"/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/file.py", 
line 88, in write
return util.uninterruptible(self._fio.write, buf)
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/util.py", 
line 20, in uninterruptible
return func(*args)
OSError: [Errno 28] No space left on device

-- Log2:
# cat /var/log/vdsm/vdsm.log
2021-05-07 10:29:49,813-0500 DEBUG (v2v/57f84423) [root] START thread 
 (func=>, args=(), 
kwargs={}) (concurrent:258)
2021-05-07 10:29:49,813-0500 INFO  (v2v/57f84423) [root] Job 
'57f84423-56cb-4187-86e2-f4208348e1f5' starting import (v2v:880)
2021-05-07 10:29:49,814-0500 DEBUG (v2v/57f84423) [storage.TaskManager.Task] 
(Task='58a7bdc0-0f7e-4307-92ba-040f1a272721') moving from state preparing -> 
state preparing (task:624)
2021-05-07 10:29:49,814-0500 INFO  (v2v/57f84423) [vdsm.api] START 
prepareImage(sdUUID='cc9fae8e-b714-44cf-9dac-3a83a15b0455', 
spUUID='24d9d2fa-98f9-11eb-aea7-00163e09cc71', 
imgUUID='226cc137-1992-4246-9484-80a1bfb5e9f7', 
leafUUID='847bc460-1b54-4756-8ced-4b969c399900', allowIllegal=False) 
from=internal, task_id=58a7bdc0-0f7e-4307-92ba-040f1a272721 (api:48)
2021-05-07 10:29:49,814-0500 DEBUG (v2v/57f84423) [storage.ResourceManager] 
Trying to register resource '00_storage.cc9fae8e-b714-44cf-9dac-3a83a15b0455' 
for lock type 'shared' (resourceManager:474)
2021-05-07 10:29:49,814-0500 DEBUG (v2v/57f84423) [storage.ResourceManager] 
Resource '00_storage.cc9fae8e-b714-44cf-9dac-3a83a15b0455' is free. Now locking 
as 'shared' (1 active user) (resourceManager:531)
2021-05-07 10:29:49,814-0500 DEBUG (v2v/57f84423) 
[storage.ResourceManager.Request] 
(ResName='00_storage.cc9fae8e-b714-44cf-9dac-3a83a15b0455', 
ReqID='b2ebef3c-8b3d-4429-b9da-b6f3af2c9ac4') Granted request 
(resourceManager:221)
2021-05-07 10:29:49,814-0500 DEBUG (v2v/57f84423) [storage.TaskManager.Task] 
(Task='58a7bdc0-0f7e-4307-92ba-040f1a272721') _resourcesAcquired: 
00_storage.cc9fae8e-b714-44cf-9dac-3a83a15b0455 (shared) (task:856)
2021-05-07 10:29:49,814-0500 DEBUG (v2v/57f84423) [storage.TaskManager.Task] 
(Task='58a7bdc0-0f7e-4307-92ba-040f1a272721') ref 1 aborting False (task:1008)
2021-05-07 10:29:49,815-0500 DEBUG (v2v/57f84423) [common.commands] 
/usr/bin/taskset --cpu-list 0-23 /usr/bin/sudo -n /sbin/lvm lvs --config 
'devices {  preferred_names=["^/dev/mapper/"]  ignore_suspended_devices=1  
write_cache_state=0  disable_after_error_count=3  
filter=["a|^/dev/mapper/360060e8007dfc830dfc8113f$|", "r|.*|"]  
hints="none"  obtain_device_list_from_udev=0 } global {  locking_type=1  
prioritise_write_locks=1  wait_for_locks=1  use_lvmetad=0 } backup {  
retain_min=50  retain_days=0 }' --noheadings --units b --nosuffix --separator 
'|' --ignoreskippedcluster -o 
uuid,name,vg_name,attr,size,seg_start_pe,devices,tags 
cc9fae8e-b714-44cf-9dac-3a83a15b0455 (cwd None) (commands:153)
2021-05-07 10:29:49,900-0500 DEBUG (v2v/57f84423) [common.commands] SUCCESS: 
 = b'';  = 0 (commands:185)
2021-05-07 10:29:49,902-0500 DEBUG (v2v/57f84423) [storage.LVM] lvs reloaded 
(lvm:759)
2021-05-07 10:29:49,904-0500 DEBUG (v2v/57f84423) [storage.Misc.excCmd] 
/usr/bin/taskset --cpu-list 0-23 /usr/bin/dd iflag=direct skip=2096 bs=512 
if=/dev/cc9fae8e-b714-44cf-9dac-3a83a15b0455/metadata count=1 (cwd None) 
(commands:211)
2021-05-07 10:29:49,916-0500 DEBUG (v2v/57f84423) [storage.Misc.excCmd] 
SUCCESS:  = b'1+0 records in\n1+0 records out\n512 bytes copied, 
0.000228452 s, 2.2 MB/s\n';  = 0 (commands:224)
2021-05-07 10:29:49,916-0500 DEBUG (v2v/57f84423) [storage.Misc] err: [b'1+0 
records in', b'1+0 records out', b'512 bytes copied,

Re: [ovirt-users] Importing VM fails with "No space left on device"

2018-03-08 Thread Michal Skrivanek 


> On 6 Mar 2018, at 11:41, Nicolas Ecarnot  wrote:
> 
> Hello,
> 
> When importing a VM, I'm facing the know bug :
> https://access.redhat.com/solutions/2770791
> 
> QImgError: ecode=1, stdout=[], stderr=['qemu-img: error while writing sector 
> 93569024: No space left on device'
> 
> The difference between my case and what is described in the RH webpage is 
> that I have no "Failed to flush the refcount block cache".
> 
> Here is what I see :
> 
>> ecfbd1a4-f9d2-463a-ade6-def5bd217b43::DEBUG::2018-03-06 
>> 09:57:36,460::utils::718::root::(watchCmd) FAILED:  = ['qemu-img: error 
>> while writing sector 205517952: No space left on device'];  = 1
>> ecfbd1a4-f9d2-463a-ade6-def5bd217b43::ERROR::2018-03-06 
>> 09:57:36,460::image::865::Storage.Image::(copyCollapsed) conversion failure 
>> for volume ac08bc8d-1eea-449a-a102-cf763c6726c8 Traceback (most recent call 
>> last):
>>  File "/usr/share/vdsm/storage/image.py", line 860, in copyCollapsed
>>volume.fmt2str(dstVolFormat))
>>  File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 207, in 
>> convert
>>raise QImgError(rc, out, err)
>> QImgError: ecode=1, stdout=[], stderr=['qemu-img: error while writing sector 
>> 205517952: No space left on device'], message=None
>> ecfbd1a4-f9d2-463a-ade6-def5bd217b43::ERROR::2018-03-06 
>> 09:57:36,461::image::878::Storage.Image::(copyCollapsed) Unexpected error
>> Traceback (most recent call last):
>>  File "/usr/share/vdsm/storage/image.py", line 866, in copyCollapsed
>>raise se.CopyImageError(str(e))
>> CopyImageError: low level Image copy failed: ("ecode=1, stdout=[], 
>> stderr=['qemu-img: error while writing sector 205517952: No space left on 
>> device'], message=None",)
> 
> I followed the advices in the RH webpage (check if the figures are correct 
> between the qemu-img sizes and the meta-data file), and they seem to be 
> correct :
> 
> root@serv-hv-adm30:/etc# qemu-img info 
> /rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr\:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8
> image: 
> /rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8
> file format: qcow2
> virtual size: 98G (105226698752 bytes)
> disk size: 97G
> cluster_size: 65536
> Format specific information:
>compat: 0.10
>refcount bits: 16
> 
> root@serv-hv-adm30:/etc# cat 
> /rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr\:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8.meta
>  DOMAIN=be2878c9-2c46-476b-bfae-8b02a4679022
> CTIME=1520318755
> FORMAT=COW
> DISKTYPE=1
> LEGALITY=LEGAL
> SIZE=205520896
> VOLTYPE=LEAF
> DESCRIPTION=
> IMAGE=a5d68d88-3b54-488d-a61e-7995a1906994
> PUUID=----
> MTIME=0
> POOL_UUID=
> TYPE=SPARSE
> EOF
> 
> 
> So I don't see what's wrong?

worth sharing with libguestfs users list, please attach the v2v logs (and 
versions used) so they can take a look

> 
> -- 
> Nicolas ECARNOT
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Importing VM fails with "No space left on device"

2018-03-06 Thread Nicolas Ecarnot 

Hello,

When importing a VM, I'm facing the know bug :
https://access.redhat.com/solutions/2770791

QImgError: ecode=1, stdout=[], stderr=['qemu-img: error while writing 
sector 93569024: No space left on device'


The difference between my case and what is described in the RH webpage 
is that I have no "Failed to flush the refcount block cache".


Here is what I see :


ecfbd1a4-f9d2-463a-ade6-def5bd217b43::DEBUG::2018-03-06 
09:57:36,460::utils::718::root::(watchCmd) FAILED:  = ['qemu-img: error while 
writing sector 205517952: No space left on device'];  = 1
ecfbd1a4-f9d2-463a-ade6-def5bd217b43::ERROR::2018-03-06 09:57:36,460::image::865::Storage.Image::(copyCollapsed) conversion failure for volume ac08bc8d-1eea-449a-a102-cf763c6726c8 
Traceback (most recent call last):

  File "/usr/share/vdsm/storage/image.py", line 860, in copyCollapsed
volume.fmt2str(dstVolFormat))
  File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 207, in convert
raise QImgError(rc, out, err)
QImgError: ecode=1, stdout=[], stderr=['qemu-img: error while writing sector 
205517952: No space left on device'], message=None
ecfbd1a4-f9d2-463a-ade6-def5bd217b43::ERROR::2018-03-06 
09:57:36,461::image::878::Storage.Image::(copyCollapsed) Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/image.py", line 866, in copyCollapsed
raise se.CopyImageError(str(e))
CopyImageError: low level Image copy failed: ("ecode=1, stdout=[], 
stderr=['qemu-img: error while writing sector 205517952: No space left on device'], 
message=None",)


I followed the advices in the RH webpage (check if the figures are 
correct between the qemu-img sizes and the meta-data file), and they 
seem to be correct :


root@serv-hv-adm30:/etc# qemu-img info 
/rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr\:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8
image: 
/rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8

file format: qcow2
virtual size: 98G (105226698752 bytes)
disk size: 97G
cluster_size: 65536
Format specific information:
compat: 0.10
refcount bits: 16

root@serv-hv-adm30:/etc# cat 
/rhev/data-center/mnt/serv-lin-adm1.sdis.isere.fr\:_home_vmexport3/be2878c9-2c46-476b-bfae-8b02a4679022/images/a5d68d88-3b54-488d-a61e-7995a1906994/ac08bc8d-1eea-449a-a102-cf763c6726c8.meta 
DOMAIN=be2878c9-2c46-476b-bfae-8b02a4679022

CTIME=1520318755
FORMAT=COW
DISKTYPE=1
LEGALITY=LEGAL
SIZE=205520896
VOLTYPE=LEAF
DESCRIPTION=
IMAGE=a5d68d88-3b54-488d-a61e-7995a1906994
PUUID=----
MTIME=0
POOL_UUID=
TYPE=SPARSE
EOF


So I don't see what's wrong?

--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users