[ovirt-users] Re: What is this error message from?
I don't recall running any convert operations on the host and certainly not on
the time/date listed. *If* I ran any conversions were run, they were run from
a laptop and then I moved the converted disk to this host. I definitely didn't
make any volume changes. Is this image conversion part of the template
process? I have been creating quite a few templates lately. I have noted that
several of them failed and I had to rerun the process. Is this some sort of
process that just keeps trying over and over because it thinks it failed?
That's the only theory I can come up with.
From: Kevin Wolf
Sent: Tuesday, February 18, 2020 3:01 AM
To: Nir Soffer
Cc: jeremy_tourvi...@hotmail.com ; users
; Krutika Dhananjay
Subject: Re: [ovirt-users] What is this error message from?
Am 17.02.2020 um 16:16 hat Nir Soffer geschrieben:
> On Mon, Feb 17, 2020, 16:53 wrote:
>
> > I have seen this error message repeatedly when reviewing events.
> >
> > VDSM vmh.cyber-range.lan command HSMGetAllTasksStatusesVDS failed: low
> > level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p',
> > '-t', 'none', '-T', 'none', '-f', 'raw',
> > u'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/c651575f-75a0-492e-959e-8cfee6b6a7b5/9b5601fe-9627-4a8a-8a98-4959f68fb137',
> > '-O', 'qcow2', '-o', 'compat=1.1',
> > u'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/6a2ce11a-deec-41e0-a726-9de6ba6d4ddd/6d738c08-0f8c-4a10-95cd-eeaa2d638db5']
> > failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading
> > sector 24117243: No such file or directory\\n')",)
> >
>
> Looks like copying image failed with ENOENT while reading
> offset 12348028416 (11.49 GiB).
>
> I never seen such failure, typically after opening a file read will never
> fail with such error, but in gluster this may be possible.
>
> Please share vdsm log showingn this error, it may add useful info.
>
> Also glusterfs client logs from
> /var/log/glusterfs*/*storage.cyber-range.lan*.log
>
> Kevin, Krutika, do you have an idea about this error?
This is a weird one. Not only that reading shouldn't be looking up any
filename, but also that it's not at offset 0, but suddenly somewhere in
the middle of the image file.
I think it's pretty safe to say that this error doesn't come from QEMU,
but from the kernel. Did you (or some software) change anything about
the volume in the background while the convert operation was running?
Kevin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/THXY23PVOWNCEQ7QUWNQGHSLMZLMLRW5/
[ovirt-users] Re: What is this error message from?
On Tue, Feb 18, 2020 at 4:13 PM Jeremy Tourville
wrote:
>
> I don't recall running any convert operations on the host and certainly not
> on the time/date listed. *If* I ran any conversions were run, they were run
> from a laptop and then I moved the converted disk to this host. I definitely
> didn't make any volume changes. Is this image conversion part of the
> template process? I have been creating quite a few templates lately. I have
> noted that several of them failed and I had to rerun the process.
This may be an error from template creation.
> Is this some sort of process that just keeps trying over and over because it
> thinks it failed?
We don't have such jobs.
The log you posted contains output from getAllTasksStatuses:
2020-02-17 06:19:47,782-0600 INFO (jsonrpc/5) [vdsm.api] FINISH
getAllTasksStatuses return={'allTasksStatus':
{'1cbc63d7-2310-4291-8f08-df5bf58376bb': {'code': 0, 'message': '1
jobs completed successfully', 'taskState': 'finished', 'taskResult':
'success', 'taskID': '1cbc63d7-2310-4291-8f08-df5bf58376bb'},
'9db209be-8e33-4c35-be8a-a58b4819812a': {'code': 261, 'message': 'low
level Image copy failed: ("Command [\'/usr/bin/qemu-img\',
\'convert\', \'-p\', \'-t\', \'none\', \'-T\', \'none\', \'-f\',
\'raw\',
u\'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/c651575f-75a0-492e-959e-8cfee6b6a7b5/9b5601fe-9627-4a8a-8a98-4959f68fb137\',
\'-O\', \'qcow2\', \'-o\', \'compat=1.1\',
u\'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/6a2ce11a-deec-41e0-a726-9de6ba6d4ddd/6d738c08-0f8c-4a10-95cd-eeaa2d638db5\']
failed with rc=1 out=\'\' err=bytearray(b\'qemu-img: error while
reading sector 24117243: No such file or directoryn\')",)',
'taskState': 'finished', 'taskResult': 'cleanSuccess', 'taskID':
'9db209be-8e33-4c35-be8a-a58b4819812a'},
'bd494f24-ca73-4e89-8ad0-629ad32bb2c1': {'code': 0, 'message': '1 jobs
completed successfully', 'taskState': 'finished', 'taskResult':
'success', 'taskID': 'bd494f24-ca73-4e89-8ad0-629ad32bb2c1'}}}
from=:::172.30.50.4,33302,
task_id=8a8c6402-4e1d-46b8-a8fd-454fde7151d7 (api:54)
The failing task was:
\'9db209be-8e33-4c35-be8a-a58b4819812a\': {
\'code\': 261,
\'message\': \'low level Image copy failed: ("Command
[\'/usr/bin/qemu-img\', \'convert\', \'-p\', \'-t\', \'none\', \'-T\',
\'none\', \'-f\', \'raw\',
u\'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/c651575f-75a0-492e-959e-8cfee6b6a7b5/9b5601fe-9627-4a8a-8a98-4959f68fb137\',
\'-O\', \'qcow2\', \'-o\', \'compat=1.1\',
u\'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/6a2ce11a-deec-41e0-a726-9de6ba6d4ddd/6d738c08-0f8c-4a10-95cd-eeaa2d638db5\']
failed with rc=1 out=\'\' err=bytearray(b\'qemu-img: error while
reading sector 24117243: No such file or directoryn\')",)\',
\'taskState\': \'finished\',
\'taskResult\': \'cleanSuccess\',
\'taskID\': \'9db209be-8e33-4c35-be8a-a58b4819812a\'
}
You may grep for this task id in all logs and share the matching logs.
Note that you have binary data in your logs, so you need to use "grep -a".
That's the only theory I can come up with.
>
>
> From: Kevin Wolf
> Sent: Tuesday, February 18, 2020 3:01 AM
> To: Nir Soffer
> Cc: jeremy_tourvi...@hotmail.com ; users
> ; Krutika Dhananjay
> Subject: Re: [ovirt-users] What is this error message from?
>
> Am 17.02.2020 um 16:16 hat Nir Soffer geschrieben:
> > On Mon, Feb 17, 2020, 16:53 wrote:
> >
> > > I have seen this error message repeatedly when reviewing events.
> > >
> > > VDSM vmh.cyber-range.lan command HSMGetAllTasksStatusesVDS failed: low
> > > level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p',
> > > '-t', 'none', '-T', 'none', '-f', 'raw',
> > > u'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/c651575f-75a0-492e-959e-8cfee6b6a7b5/9b5601fe-9627-4a8a-8a98-4959f68fb137',
> > > '-O', 'qcow2', '-o', 'compat=1.1',
> > > u'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/6a2ce11a-deec-41e0-a726-9de6ba6d4ddd/6d738c08-0f8c-4a10-95cd-eeaa2d638db5']
> > > failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading
> > > sector 24117243: No such file or directory\\n')",)
> > >
> >
> > Looks like copying image failed with ENOENT while reading
> > offset 12348028416 (11.49 GiB).
> >
> > I never seen such failure, typically after opening a file read will
[ovirt-users] Re: What is this error message from?
Am 17.02.2020 um 16:16 hat Nir Soffer geschrieben:
> On Mon, Feb 17, 2020, 16:53 wrote:
>
> > I have seen this error message repeatedly when reviewing events.
> >
> > VDSM vmh.cyber-range.lan command HSMGetAllTasksStatusesVDS failed: low
> > level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p',
> > '-t', 'none', '-T', 'none', '-f', 'raw',
> > u'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/c651575f-75a0-492e-959e-8cfee6b6a7b5/9b5601fe-9627-4a8a-8a98-4959f68fb137',
> > '-O', 'qcow2', '-o', 'compat=1.1',
> > u'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/6a2ce11a-deec-41e0-a726-9de6ba6d4ddd/6d738c08-0f8c-4a10-95cd-eeaa2d638db5']
> > failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading
> > sector 24117243: No such file or directory\\n')",)
> >
>
> Looks like copying image failed with ENOENT while reading
> offset 12348028416 (11.49 GiB).
>
> I never seen such failure, typically after opening a file read will never
> fail with such error, but in gluster this may be possible.
>
> Please share vdsm log showingn this error, it may add useful info.
>
> Also glusterfs client logs from
> /var/log/glusterfs*/*storage.cyber-range.lan*.log
>
> Kevin, Krutika, do you have an idea about this error?
This is a weird one. Not only that reading shouldn't be looking up any
filename, but also that it's not at offset 0, but suddenly somewhere in
the middle of the image file.
I think it's pretty safe to say that this error doesn't come from QEMU,
but from the kernel. Did you (or some software) change anything about
the volume in the background while the convert operation was running?
Kevin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6C3666HJSRP5BEGTZUTV6C6A6GV2N37I/
[ovirt-users] Re: What is this error message from?
On Mon, Feb 17, 2020, 16:53 wrote:
> I have seen this error message repeatedly when reviewing events.
>
> VDSM vmh.cyber-range.lan command HSMGetAllTasksStatusesVDS failed: low
> level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p',
> '-t', 'none', '-T', 'none', '-f', 'raw',
> u'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/c651575f-75a0-492e-959e-8cfee6b6a7b5/9b5601fe-9627-4a8a-8a98-4959f68fb137',
> '-O', 'qcow2', '-o', 'compat=1.1',
> u'/rhev/data-center/mnt/glusterSD/storage.cyber-range.lan:_vmstore/dd69364b-2c02-4165-bc4b-2f2a3b7fc10d/images/6a2ce11a-deec-41e0-a726-9de6ba6d4ddd/6d738c08-0f8c-4a10-95cd-eeaa2d638db5']
> failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading
> sector 24117243: No such file or directory\\n')",)
>
Looks like copying image failed with ENOENT while reading
offset 12348028416 (11.49 GiB).
I never seen such failure, typically after opening a file read will never
fail with such error, but in gluster this may be possible.
Please share vdsm log showingn this error, it may add useful info.
Also glusterfs client logs from
/var/log/glusterfs*/*storage.cyber-range.lan*.log
Kevin, Krutika, do you have an idea about this error?
Nir
> Can someone explain what this is? How do I get this cleared up/resolved?
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/KBNSTWBZFN7PGWW74AGAGQVPNJ2DIZ6S/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/67N6VIO47YSMQ6VHWKZZWLYETPK4HC2I/
