[ovirt-users] Re: Bad volume specification

2020-09-18 Thread Facundo Garat
Vojtech, thanks for this info I will try that. On Fri, 18 Sep 2020 at 6:31 AM Vojtech Juranek wrote: > On čtvrtek 17. září 2020 16:07:16 CEST Facundo Garat wrote: > > > I don't think so, We have bigger LUNs assigned so if that were the case > we > > > would have lost access to many LVs. > > > >

[ovirt-users] Re: Bad volume specification

2020-09-18 Thread Vojtech Juranek
On čtvrtek 17. září 2020 16:07:16 CEST Facundo Garat wrote: > I don't think so, We have bigger LUNs assigned so if that were the case we > would have lost access to many LVs. > > Do I have a way to manually query the LVs content to find out if it's still > there?. you can ssh to a host and check

[ovirt-users] Re: Bad volume specification

2020-09-17 Thread Facundo Garat
I don't think so, We have bigger LUNs assigned so if that were the case we would have lost access to many LVs. Do I have a way to manually query the LVs content to find out if it's still there?. On Thu, Sep 17, 2020 at 10:55 AM Vojtech Juranek wrote: > On čtvrtek 17. září 2020 14:30:12 CEST

[ovirt-users] Re: Bad volume specification

2020-09-17 Thread Vojtech Juranek
On čtvrtek 17. září 2020 14:30:12 CEST Facundo Garat wrote: > Hi Vojtech, > find the log attached. thanks. It fails as one of the image volumes (6058a880-9ee6-4c57-9db0-5946c6dab676) is now available/present on the storage. You can check manually if there's such LV, but it's not very likely.

[ovirt-users] Re: Bad volume specification

2020-09-17 Thread Vojtech Juranek
Hi, could you please send us also relevant part of vdsm log (/var/log/vdsm/ vdsm.log)? Thanks Vojta > The VM has one snapshot which I can't delete because it shows a similar > error. That doesn't allow me to attach the disks to another VM. This VM > will boot ok if the disks are deactivated. >

[ovirt-users] Re: Bad volume specification

2020-09-16 Thread Facundo Garat
The VM has one snapshot which I can't delete because it shows a similar error. That doesn't allow me to attach the disks to another VM. This VM will boot ok if the disks are deactivated. Find the engine.log attached. The steps associated with the engine log: - The VM is on booted from CD

[ovirt-users] Re: Bad volume specification

2020-09-16 Thread Ahmad Khiet
Hi, can you please attach the engine log? what steps did you make before this error is shown? did you tried to create a snapshot and failed before On Wed, Sep 16, 2020 at 7:49 AM Strahil Nikolov via Users wrote: > What happens if you create another VM and attach the disks to it ? > Does it

[ovirt-users] Re: Bad volume specification

2020-09-15 Thread Strahil Nikolov via Users
What happens if you create another VM and attach the disks to it ? Does it boot properly ? Best Regards, Strahil Nikolov В сряда, 16 септември 2020 г., 02:19:26 Гринуич+3, Facundo Garat написа: Hi all,  I'm having some issues with one VM. The VM won't start and it's showing

[ovirt-users] Re: Bad volume specification

2018-05-28 Thread Bryan Sockel
Permissions all seem to be correct, path is accessible, can run other vm's off the same storage domain. Thank You, From: "Oliver Riesener (oliver.riese...@hs-bremen.de)" To: Bryan Sockel Cc: "users@ovirt.org" Date: Sun, 27 May 2018 15:38:32 +0200 Subject: [ovirt-u

[ovirt-users] Re: Bad volume specification

2018-05-27 Thread Oliver Riesener
Hi, check what wrong with your **PATH**: permissions, lvm, device-mapper, NFS, iSCSI, etc. > Am 27.05.2018 um 15:28 schrieb Bryan Sockel : > > 'path': >