Re: [ovirt-users] Cannot activate storage domain

2018-03-11 Thread Bruckner, Simone
Shani,

  all storage domains are FC.

In the meantime I could track it down to corrupt vg metadata. I filed a bug 
(https://bugzilla.redhat.com/show_bug.cgi?id=1553133).

I ran vgcfgrestore, copied the VMs I could recover and recreated the LUNs. 
Would there have been another way of recovering?

All the best,
Simone

Von: Shani Leviim [mailto:slev...@redhat.com]
Gesendet: Sonntag, 11. März 2018 14:09
An: Bruckner, Simone <simone.bruck...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi Simone,
Sorry for the delay replying you.

Does the second storage domain you've mentioned is also an FC?
If so, please execute the following command  /usr/libexec/vdsm/fc-scan -v
on one host of each inactive storage domain and share the results you've got.


Regards,
Shani Leviim

On Thu, Mar 8, 2018 at 9:42 AM, Bruckner, Simone 
<simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>> wrote:
Hi Shani,

  today I again lost access to a storage domain. So currently I have two 
storage domains that we cannot activate any more.

I uploaded the logfiles to our Cloud Service: [ZIP Archive]  
logfiles.tar.gz<https://at.cloud.fabasoft.com/folio/public/1zf8q45o1e9l8334agryb2crdd>
I lost access today, March 8th 2018 around 0.55am CET
I tried to actived the storage domain around 6.40am CET

Please let me know if there is anything I can do to get this addressed.

Thank you very much,
Simone



Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>]" im Auftrag von 
"Bruckner, Simone 
[simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>]
Gesendet: Dienstag, 06. März 2018 10:19
An: Shani Leviim
Cc: users@ovirt.org<mailto:users@ovirt.org>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi Shani,

  please find the logs attached.

Thank you,
Simone

Von: Shani Leviim [mailto:slev...@redhat.com<mailto:slev...@redhat.com>]
Gesendet: Dienstag, 6. März 2018 09:48
An: Bruckner, Simone 
<simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>>
Cc: users@ovirt.org<mailto:users@ovirt.org>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi Simone,
Can you please share your vdsm and engine logs?

Regards,
Shani Leviim

On Tue, Mar 6, 2018 at 7:34 AM, Bruckner, Simone 
<simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com><mailto:simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>>>
 wrote:
Hello, I apologize for bringing this one up again, but does anybody know if 
there is a change to recover a storage domain, that cannot be activated?

Thank you,
Simone

Von: 
users-boun...@ovirt.org<mailto:users-boun...@ovirt.org><mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>>
 
[mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org><mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>>]
 Im Auftrag von Bruckner, Simone
Gesendet: Freitag, 2. März 2018 17:03

An: 
users@ovirt.org<mailto:users@ovirt.org><mailto:users@ovirt.org<mailto:users@ovirt.org>>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi all,

  I managed to get the inactive storage domain to maintenance by stopping all 
running VMs that were using it, but I am still not able to activate it.

Trying to activate results in the following events:

For each host:
VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And finally:
VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)

Is there anything I can do to recover this storage domain?

Thank you and all the best,
Simone

Von: 
users-boun...@ovirt.org<mailto:users-boun...@ovirt.org><mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>>
 [mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>] Im Auftrag 
von Bruckner, Simone
Gesendet: Donnerstag, 1. März 2018 17:57
An: 
users@ovirt.org<mailto:users@ovirt.org><mailto:users@ovirt.org<mailto:users@ovirt.org>>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi,

  we are still struggling getting a storage domain online again. We tried to 
put the storage domain in maintenance mode, that led to “Failed to update OVF 
disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't updated on those OVF 
stores”.

Trying again with ignoring OVF update failures put the storage domain in 
“preparing for maintenance”. We see the following message on all hosts: “Error 
releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 
(monitor:578)”.

Querying the storage domain using vdsm-client on the SPM resulted in
# vdsm-client StorageDomain getInfo 
"storagedomainID&quo

Re: [ovirt-users] Cannot activate storage domain

2018-03-11 Thread Shani Leviim
Hi Simone,

Sorry for the delay replying you.

Does the second storage domain you've mentioned is also an FC?

If so, please execute the following command  /usr/libexec/vdsm/fc-scan -v
on one host of each inactive storage domain and share the results you've
got.




*Regards,*

*Shani Leviim*

On Thu, Mar 8, 2018 at 9:42 AM, Bruckner, Simone <
simone.bruck...@fabasoft.com> wrote:

> Hi Shani,
>
>   today I again lost access to a storage domain. So currently I have two
> storage domains that we cannot activate any more.
>
> I uploaded the logfiles to our Cloud Service: [ZIP Archive]
> logfiles.tar.gz<https://at.cloud.fabasoft.com/folio/public/
> 1zf8q45o1e9l8334agryb2crdd>
> I lost access today, March 8th 2018 around 0.55am CET
> I tried to actived the storage domain around 6.40am CET
>
> Please let me know if there is anything I can do to get this addressed.
>
> Thank you very much,
> Simone
>
>
> 
> Von: users-boun...@ovirt.org [users-boun...@ovirt.org]" im Auftrag von
> "Bruckner, Simone [simone.bruck...@fabasoft.com]
> Gesendet: Dienstag, 06. März 2018 10:19
> An: Shani Leviim
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Cannot activate storage domain
>
> Hi Shani,
>
>   please find the logs attached.
>
> Thank you,
> Simone
>
> Von: Shani Leviim [mailto:slev...@redhat.com]
> Gesendet: Dienstag, 6. März 2018 09:48
> An: Bruckner, Simone <simone.bruck...@fabasoft.com>
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Cannot activate storage domain
>
> Hi Simone,
> Can you please share your vdsm and engine logs?
>
> Regards,
> Shani Leviim
>
> On Tue, Mar 6, 2018 at 7:34 AM, Bruckner, Simone <
> simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>> wrote:
> Hello, I apologize for bringing this one up again, but does anybody know
> if there is a change to recover a storage domain, that cannot be activated?
>
> Thank you,
> Simone
>
> Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> [mailto:
> users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>] Im Auftrag von
> Bruckner, Simone
> Gesendet: Freitag, 2. März 2018 17:03
>
> An: users@ovirt.org<mailto:users@ovirt.org>
> Betreff: Re: [ovirt-users] Cannot activate storage domain
>
> Hi all,
>
>   I managed to get the inactive storage domain to maintenance by stopping
> all running VMs that were using it, but I am still not able to activate it.
>
> Trying to activate results in the following events:
>
> For each host:
> VDSM  command GetVGInfoVDS failed: Volume Group does not exist:
> (u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)
>
> And finally:
> VDSM command ActivateStorageDomainVDS failed: Storage domain does not
> exist: (u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
>
> Is there anything I can do to recover this storage domain?
>
> Thank you and all the best,
> Simone
>
> Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> [mailto:
> users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
> Gesendet: Donnerstag, 1. März 2018 17:57
> An: users@ovirt.org<mailto:users@ovirt.org>
> Betreff: Re: [ovirt-users] Cannot activate storage domain
>
> Hi,
>
>   we are still struggling getting a storage domain online again. We tried
> to put the storage domain in maintenance mode, that led to “Failed to
> update OVF disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't
> updated on those OVF stores”.
>
> Trying again with ignoring OVF update failures put the storage domain in
> “preparing for maintenance”. We see the following message on all hosts:
> “Error releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0
> (monitor:578)”.
>
> Querying the storage domain using vdsm-client on the SPM resulted in
> # vdsm-client StorageDomain getInfo "storagedomainID"="b83c159c-
> 4ad6-4613-ba16-bab95ccd10c0"
> vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID':
> 'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
> (code=358, message=Storage domain does not exist:
> (u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',))
>
> Any ideas?
>
> Thank you and all the best,
> Simone
>
> Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> [mailto:
> users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
> Gesendet: Mittwoch, 28. Februar 2018 15:52
> An: users@ovirt.org<mailto:users@ovirt.org>
> Betreff: [ovirt-users] Cannot activate storage domain
>
> Hi all,
>
>   we run a small oVirt installation that we also use for automated testing
> (automatically creating, dropping vms).
>
> We got an inactive FC storage

Re: [ovirt-users] Cannot activate storage domain

2018-03-07 Thread Bruckner, Simone
Hi Shani,

  today I again lost access to a storage domain. So currently I have two 
storage domains that we cannot activate any more.

I uploaded the logfiles to our Cloud Service: [ZIP Archive]  
logfiles.tar.gz<https://at.cloud.fabasoft.com/folio/public/1zf8q45o1e9l8334agryb2crdd>
I lost access today, March 8th 2018 around 0.55am CET
I tried to actived the storage domain around 6.40am CET

Please let me know if there is anything I can do to get this addressed.

Thank you very much,
Simone



Von: users-boun...@ovirt.org [users-boun...@ovirt.org]" im Auftrag von 
"Bruckner, Simone [simone.bruck...@fabasoft.com]
Gesendet: Dienstag, 06. März 2018 10:19
An: Shani Leviim
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi Shani,

  please find the logs attached.

Thank you,
Simone

Von: Shani Leviim [mailto:slev...@redhat.com]
Gesendet: Dienstag, 6. März 2018 09:48
An: Bruckner, Simone <simone.bruck...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi Simone,
Can you please share your vdsm and engine logs?

Regards,
Shani Leviim

On Tue, Mar 6, 2018 at 7:34 AM, Bruckner, Simone 
<simone.bruck...@fabasoft.com<mailto:simone.bruck...@fabasoft.com>> wrote:
Hello, I apologize for bringing this one up again, but does anybody know if 
there is a change to recover a storage domain, that cannot be activated?

Thank you,
Simone

Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>] Im Auftrag von 
Bruckner, Simone
Gesendet: Freitag, 2. März 2018 17:03

An: users@ovirt.org<mailto:users@ovirt.org>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi all,

  I managed to get the inactive storage domain to maintenance by stopping all 
running VMs that were using it, but I am still not able to activate it.

Trying to activate results in the following events:

For each host:
VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And finally:
VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)

Is there anything I can do to recover this storage domain?

Thank you and all the best,
Simone

Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
Gesendet: Donnerstag, 1. März 2018 17:57
An: users@ovirt.org<mailto:users@ovirt.org>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi,

  we are still struggling getting a storage domain online again. We tried to 
put the storage domain in maintenance mode, that led to “Failed to update OVF 
disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't updated on those OVF 
stores”.

Trying again with ignoring OVF update failures put the storage domain in 
“preparing for maintenance”. We see the following message on all hosts: “Error 
releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 
(monitor:578)”.

Querying the storage domain using vdsm-client on the SPM resulted in
# vdsm-client StorageDomain getInfo 
"storagedomainID"="b83c159c-4ad6-4613-ba16-bab95ccd10c0"
vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID': 
'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
(code=358, message=Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',))

Any ideas?

Thank you and all the best,
Simone

Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
Gesendet: Mittwoch, 28. Februar 2018 15:52
An: users@ovirt.org<mailto:users@ovirt.org>
Betreff: [ovirt-users] Cannot activate storage domain

Hi all,

  we run a small oVirt installation that we also use for automated testing 
(automatically creating, dropping vms).

We got an inactive FC storage domain that we cannot activate any more. We see 
several events at that time starting with:

VM perftest-c17 is down with error. Exit message: Unable to get volume size for 
domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 volume 
686376c1-4be1-44c3-89a3-0a8addc8fdf2.

Trying to activate the strorage domain results in the following alert event for 
each host:

VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And after those messages from all hosts we get:

VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
Failed to activate Storage Domain VMHOST_LUN_205 (Data Center Production) by 

Invalid status on Data Center Production. Setting status to Non Responsive.
Storage Pool Manager runs on Host 
vmhost003.fabagl.fabasoft.com<http://vmhost003.fabagl.fabasoft.com> (Address: 
vmhost003.fabagl.fabasoft.com&l

Re: [ovirt-users] Cannot activate storage domain

2018-03-06 Thread Shani Leviim
Hi Simone,

Can you please share your vdsm and engine logs?


*Regards,*

*Shani Leviim*

On Tue, Mar 6, 2018 at 7:34 AM, Bruckner, Simone <
simone.bruck...@fabasoft.com> wrote:

> Hello, I apologize for bringing this one up again, but does anybody know
> if there is a change to recover a storage domain, that cannot be activated?
>
>
>
> Thank you,
>
> Simone
>
>
>
> *Von:* users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] *Im
> Auftrag von *Bruckner, Simone
> *Gesendet:* Freitag, 2. März 2018 17:03
>
> *An:* users@ovirt.org
> *Betreff:* Re: [ovirt-users] Cannot activate storage domain
>
>
>
> Hi all,
>
>
>
>   I managed to get the inactive storage domain to maintenance by stopping
> all running VMs that were using it, but I am still not able to activate it.
>
>
>
> Trying to activate results in the following events:
>
>
>
> For each host:
>
> VDSM  command GetVGInfoVDS failed: Volume Group does not exist:
> (u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)
>
>
>
> And finally:
>
> VDSM command ActivateStorageDomainVDS failed: Storage domain does not
> exist: (u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
>
>
>
> Is there anything I can do to recover this storage domain?
>
>
>
> Thank you and all the best,
>
> Simone
>
>
>
> *Von:* users-boun...@ovirt.org [mailto:users-boun...@ovirt.org
> <users-boun...@ovirt.org>] *Im Auftrag von *Bruckner, Simone
> *Gesendet:* Donnerstag, 1. März 2018 17:57
> *An:* users@ovirt.org
> *Betreff:* Re: [ovirt-users] Cannot activate storage domain
>
>
>
> Hi,
>
>
>
>   we are still struggling getting a storage domain online again. We tried
> to put the storage domain in maintenance mode, that led to “Failed to
> update OVF disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't
> updated on those OVF stores”.
>
>
>
> Trying again with ignoring OVF update failures put the storage domain in
> “preparing for maintenance”. We see the following message on all hosts:
> “Error releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0
> (monitor:578)”.
>
>
>
> Querying the storage domain using vdsm-client on the SPM resulted in
>
> # vdsm-client StorageDomain getInfo "storagedomainID"="b83c159c-
> 4ad6-4613-ba16-bab95ccd10c0"
>
> vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID':
> 'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
>
> (code=358, message=Storage domain does not exist:
> (u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',))
>
>
>
> Any ideas?
>
>
>
> Thank you and all the best,
>
> Simone
>
>
>
> *Von:* users-boun...@ovirt.org [mailto:users-boun...@ovirt.org
> <users-boun...@ovirt.org>] *Im Auftrag von *Bruckner, Simone
> *Gesendet:* Mittwoch, 28. Februar 2018 15:52
> *An:* users@ovirt.org
> *Betreff:* [ovirt-users] Cannot activate storage domain
>
>
>
> Hi all,
>
>
>
>   we run a small oVirt installation that we also use for automated testing
> (automatically creating, dropping vms).
>
>
>
> We got an inactive FC storage domain that we cannot activate any more. We
> see several events at that time starting with:
>
>
>
> VM perftest-c17 is down with error. Exit message: Unable to get volume
> size for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 volume
> 686376c1-4be1-44c3-89a3-0a8addc8fdf2.
>
>
>
> Trying to activate the strorage domain results in the following alert
> event for each host:
>
>
>
> VDSM  command GetVGInfoVDS failed: Volume Group does not exist:
> (u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)
>
>
>
> And after those messages from all hosts we get:
>
>
>
> VDSM command ActivateStorageDomainVDS failed: Storage domain does not
> exist: (u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
>
> Failed to activate Storage Domain VMHOST_LUN_205 (Data Center Production)
> by 
>
> Invalid status on Data Center Production. Setting status to Non Responsive.
>
> Storage Pool Manager runs on Host vmhost003.fabagl.fabasoft.com (Address:
> vmhost003.fabagl.fabasoft.com), Data Center Production.
>
>
>
> Checking the hosts with multipath –ll we see the LUN without errors.
>
>
>
> We run oVirt 4.2.1 on CentOS 7.4. Hosts are CentOS 7.4 hosts with oVirt
> installed using oVirt engine.
>
> Hosts are connected to about 30 FC LUNs (8 TB each) on two all-flash
> storage arrays.
>
>
>
> Thank you,
>
> Simone Bruckner
>
>
>
>
>
>
>
> ___
> 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


Re: [ovirt-users] Cannot activate storage domain

2018-03-05 Thread Bruckner, Simone
Hello, I apologize for bringing this one up again, but does anybody know if 
there is a change to recover a storage domain, that cannot be activated?

Thank you,
Simone

Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Bruckner, Simone
Gesendet: Freitag, 2. März 2018 17:03
An: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi all,

  I managed to get the inactive storage domain to maintenance by stopping all 
running VMs that were using it, but I am still not able to activate it.

Trying to activate results in the following events:

For each host:
VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And finally:
VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)

Is there anything I can do to recover this storage domain?

Thank you and all the best,
Simone

Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
Gesendet: Donnerstag, 1. März 2018 17:57
An: users@ovirt.org<mailto:users@ovirt.org>
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi,

  we are still struggling getting a storage domain online again. We tried to 
put the storage domain in maintenance mode, that led to "Failed to update OVF 
disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't updated on those OVF 
stores".

Trying again with ignoring OVF update failures put the storage domain in 
"preparing for maintenance". We see the following message on all hosts: "Error 
releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 
(monitor:578)".

Querying the storage domain using vdsm-client on the SPM resulted in
# vdsm-client StorageDomain getInfo 
"storagedomainID"="b83c159c-4ad6-4613-ba16-bab95ccd10c0"
vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID': 
'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
(code=358, message=Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',))

Any ideas?

Thank you and all the best,
Simone

Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
Gesendet: Mittwoch, 28. Februar 2018 15:52
An: users@ovirt.org<mailto:users@ovirt.org>
Betreff: [ovirt-users] Cannot activate storage domain

Hi all,

  we run a small oVirt installation that we also use for automated testing 
(automatically creating, dropping vms).

We got an inactive FC storage domain that we cannot activate any more. We see 
several events at that time starting with:

VM perftest-c17 is down with error. Exit message: Unable to get volume size for 
domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 volume 
686376c1-4be1-44c3-89a3-0a8addc8fdf2.

Trying to activate the strorage domain results in the following alert event for 
each host:

VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And after those messages from all hosts we get:

VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
Failed to activate Storage Domain VMHOST_LUN_205 (Data Center Production) by 

Invalid status on Data Center Production. Setting status to Non Responsive.
Storage Pool Manager runs on Host vmhost003.fabagl.fabasoft.com (Address: 
vmhost003.fabagl.fabasoft.com), Data Center Production.

Checking the hosts with multipath -ll we see the LUN without errors.

We run oVirt 4.2.1 on CentOS 7.4. Hosts are CentOS 7.4 hosts with oVirt 
installed using oVirt engine.
Hosts are connected to about 30 FC LUNs (8 TB each) on two all-flash storage 
arrays.

Thank you,
Simone Bruckner



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


Re: [ovirt-users] Cannot activate storage domain

2018-03-02 Thread Bruckner, Simone
Hi all,

  I managed to get the inactive storage domain to maintenance by stopping all 
running VMs that were using it, but I am still not able to activate it.

Trying to activate results in the following events:

For each host:
VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And finally:
VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)

Is there anything I can do to recover this storage domain?

Thank you and all the best,
Simone

Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Bruckner, Simone
Gesendet: Donnerstag, 1. März 2018 17:57
An: users@ovirt.org
Betreff: Re: [ovirt-users] Cannot activate storage domain

Hi,

  we are still struggling getting a storage domain online again. We tried to 
put the storage domain in maintenance mode, that led to "Failed to update OVF 
disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't updated on those OVF 
stores".

Trying again with ignoring OVF update failures put the storage domain in 
"preparing for maintenance". We see the following message on all hosts: "Error 
releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 
(monitor:578)".

Querying the storage domain using vdsm-client on the SPM resulted in
# vdsm-client StorageDomain getInfo 
"storagedomainID"="b83c159c-4ad6-4613-ba16-bab95ccd10c0"
vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID': 
'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
(code=358, message=Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',))

Any ideas?

Thank you and all the best,
Simone

Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org] Im Auftrag von Bruckner, Simone
Gesendet: Mittwoch, 28. Februar 2018 15:52
An: users@ovirt.org<mailto:users@ovirt.org>
Betreff: [ovirt-users] Cannot activate storage domain

Hi all,

  we run a small oVirt installation that we also use for automated testing 
(automatically creating, dropping vms).

We got an inactive FC storage domain that we cannot activate any more. We see 
several events at that time starting with:

VM perftest-c17 is down with error. Exit message: Unable to get volume size for 
domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 volume 
686376c1-4be1-44c3-89a3-0a8addc8fdf2.

Trying to activate the strorage domain results in the following alert event for 
each host:

VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And after those messages from all hosts we get:

VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
Failed to activate Storage Domain VMHOST_LUN_205 (Data Center Production) by 

Invalid status on Data Center Production. Setting status to Non Responsive.
Storage Pool Manager runs on Host vmhost003.fabagl.fabasoft.com (Address: 
vmhost003.fabagl.fabasoft.com), Data Center Production.

Checking the hosts with multipath -ll we see the LUN without errors.

We run oVirt 4.2.1 on CentOS 7.4. Hosts are CentOS 7.4 hosts with oVirt 
installed using oVirt engine.
Hosts are connected to about 30 FC LUNs (8 TB each) on two all-flash storage 
arrays.

Thank you,
Simone Bruckner



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


Re: [ovirt-users] Cannot activate storage domain

2018-03-01 Thread Bruckner, Simone
Hi,

  we are still struggling getting a storage domain online again. We tried to 
put the storage domain in maintenance mode, that led to "Failed to update OVF 
disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't updated on those OVF 
stores".

Trying again with ignoring OVF update failures put the storage domain in 
"preparing for maintenance". We see the following message on all hosts: "Error 
releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 
(monitor:578)".

Querying the storage domain using vdsm-client on the SPM resulted in
# vdsm-client StorageDomain getInfo 
"storagedomainID"="b83c159c-4ad6-4613-ba16-bab95ccd10c0"
vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID': 
'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
(code=358, message=Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',))

Any ideas?

Thank you and all the best,
Simone

Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Bruckner, Simone
Gesendet: Mittwoch, 28. Februar 2018 15:52
An: users@ovirt.org
Betreff: [ovirt-users] Cannot activate storage domain

Hi all,

  we run a small oVirt installation that we also use for automated testing 
(automatically creating, dropping vms).

We got an inactive FC storage domain that we cannot activate any more. We see 
several events at that time starting with:

VM perftest-c17 is down with error. Exit message: Unable to get volume size for 
domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 volume 
686376c1-4be1-44c3-89a3-0a8addc8fdf2.

Trying to activate the strorage domain results in the following alert event for 
each host:

VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And after those messages from all hosts we get:

VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
Failed to activate Storage Domain VMHOST_LUN_205 (Data Center Production) by 

Invalid status on Data Center Production. Setting status to Non Responsive.
Storage Pool Manager runs on Host vmhost003.fabagl.fabasoft.com (Address: 
vmhost003.fabagl.fabasoft.com), Data Center Production.

Checking the hosts with multipath -ll we see the LUN without errors.

We run oVirt 4.2.1 on CentOS 7.4. Hosts are CentOS 7.4 hosts with oVirt 
installed using oVirt engine.
Hosts are connected to about 30 FC LUNs (8 TB each) on two all-flash storage 
arrays.

Thank you,
Simone Bruckner



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


[ovirt-users] Cannot activate storage domain

2018-02-28 Thread Bruckner, Simone
Hi all,



  we run a small oVirt installation that we also use for automated testing 
(automatically creating, dropping vms).



We got an inactive FC storage domain that we cannot activate any more. We see 
several events at that time starting with:



VM perftest-c17 is down with error. Exit message: Unable to get volume size for 
domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 volume 
686376c1-4be1-44c3-89a3-0a8addc8fdf2.



Trying to activate the strorage domain results in the following alert event for 
each host:



VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)



And after those messages from all hosts we get:



VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)

Failed to activate Storage Domain VMHOST_LUN_205 (Data Center Production) by 


Invalid status on Data Center Production. Setting status to Non Responsive.

Storage Pool Manager runs on Host vmhost003.fabagl.fabasoft.com (Address: 
vmhost003.fabagl.fabasoft.com), Data Center Production.



Checking the hosts with multipath -ll we see the LUN without errors.



We run oVirt 4.2.1 on CentOS 7.4. Hosts are CentOS 7.4 hosts with oVirt 
installed using oVirt engine.

Hosts are connected to about 30 FC LUNs (8 TB each) on two all-flash storage 
arrays.



Thank you,

Simone Bruckner







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


Re: [ovirt-users] Cannot activate storage domain

2014-12-20 Thread SATHEESARAN

Hi Brent,

From your logs, I could able to see that gluster mount has become 
read-only.

This happens only two circumstances,
1. Client-side quorum is enabled on that volume and its not met
2. Client-side quorum is enabled on that volume and the first brick of 
the replica pair went down.


I think you would have met the second scenario.
Client-side quorum is enabled on gluster volume to prevent network 
partition problems which would lead to split-brain scenarios.
If you want to restore your storage domain, you can disable client-side 
quorum momentarily using RHEVM UI

or using gluster cli. ( # gluster volume reset vol-name quorum-type )

Hope that helps.

-- Satheesaran S



On 12/19/2014 01:09 PM, Sahina Bose wrote:

[+Sas - thanks for the link to virt-store usecase article inline]

On 12/18/2014 06:56 PM, Brent Hartzell wrote:

Hello,

I had actually gotten this sorted out, somewhat. If I disable server 
quorum
on the volume, the storage domain will activate. The volume is/was 
optimized

for virt store via oVirt. The brick in question was not the first brick
added to the volume through oVirt however, it appears that it may 
have been
the first brick in the replica being used, but I'm not certain how to 
find

this out.


The recommended setting is to have both client and server side quorum 
turned on. But turning on server-side quorum with a 2-way replica 
volume would mean that your volume goes offline when one of the bricks 
goes down.


gluster volume info command will give you information about the 
volume topology. So will the bricks sub-tab for Volume in oVirt. The 
order in which the bricks are listed, is the order of the replica sets.


Disabling quorum allowed me to get the VM's affected back online 
however, is
this the recommended procedure? I tried to use replace-brick with 
another

node but it failed because the failed brick was not available. Would we
leave quorum disabled until that brick gets replaced? IE - rebuild the
server with the same hostname/IP file structure and rebalance the 
cluster?


http://www.gluster.org/community/documentation/index.php/Virt-store-usecase 
- for recommendations on volume tunables.


You could add another brick to your volume to make it a replica 3 and 
then turn on quorum?


For help on recovering your volume, I suggest you write to 
gluster-us...@gluster.org







While that happened, I read somewhere about this happening with a 
replica 2
- I've created a new volume with replica 3 and plan to test this 
again. Is
there any info you can point me to for how to handle this when it 
happens or

what the correct procedure is when a first brick fails?






-Original Message-
From: Sahina Bose [mailto:sab...@redhat.com]
Sent: Thursday, December 18, 2014 3:51 AM
To: Vered Volansky; Brent Hartzell
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Cannot activate storage domain


On 12/18/2014 01:35 PM, Vered Volansky wrote:

Adding Sahina.

- Original Message -

From: Brent Hartzell brent.hartz...@outlook.com
To: users@ovirt.org
Sent: Thursday, December 18, 2014 3:38:11 AM
Subject: [ovirt-users] Cannot activate storage domain



Have the following:



6 hosts - virt + Gluster shared



Gluster volume is distributed-replicate - replica 2



Shutting down servers one at a time all work except for 1 brick. If
we shut down one specific brick (1 brick per host) - we're unable to
activate the storage domain. VM's that were actively running from
other bricks continue to run. Whatever was running form that specific
brick fails to run, gets paused etc.



Error log shows the entry below. I'm not certain what it's saying is
read only.nothing is read only that I can find.





2014-12-17 19:57:13,362 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-47) [4e9290a2] Command
SpmStatusVDSCommand(HostName = U23.domainame.net, HostId =
0db58e46-68a3-4ba0-a8aa-094893c045a1, storagePoolId =
7ccd6ea9-7d80-4170-afa1-64c10c185aa6) execution failed. Exception:
VDSErrorException: VDSGenericException: VDSErrorException: Failed to
SpmStatusVDS, error = [Errno 30] Read-only file system, code = 100

2014-12-17 19:57:13,363 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData]
(DefaultQuartzScheduler_Worker-47) [4e9290a2]
hostFromVds::selectedVds - U23.domainname.net, spmStatus returned 
null!






According to Ovirt/Gluster, if a brick goes down, the VM should be
able to be restarted from another brick without issue. This does not
appear to be the case. If we take other bricks offline, it appears to

work as expected.

Something with this specific brick cases everything to break which
then makes any VM's that were running from the brick unable to start.
Do you have the recommended options for using volume as virt store 
turned
on? Is client-side quorum turned on for the volume? Is the brick that 
causes

the issue, the first brick in the replica set?



___
Users

Re: [ovirt-users] Cannot activate storage domain

2014-12-18 Thread Vered Volansky
Adding Sahina.

- Original Message -
 From: Brent Hartzell brent.hartz...@outlook.com
 To: users@ovirt.org
 Sent: Thursday, December 18, 2014 3:38:11 AM
 Subject: [ovirt-users] Cannot activate storage domain
 
 
 
 Have the following:
 
 
 
 6 hosts – virt + Gluster shared
 
 
 
 Gluster volume is distributed-replicate – replica 2
 
 
 
 Shutting down servers one at a time all work except for 1 brick. If we shut
 down one specific brick (1 brick per host) – we’re unable to activate the
 storage domain. VM’s that were actively running from other bricks continue
 to run. Whatever was running form that specific brick fails to run, gets
 paused etc.
 
 
 
 Error log shows the entry below. I’m not certain what it’s saying is read
 only…nothing is read only that I can find.
 
 
 
 
 
 2014-12-17 19:57:13,362 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
 (DefaultQuartzScheduler_Worker-47) [4e9290a2] Command
 SpmStatusVDSCommand(HostName = U23.domainame.net, HostId =
 0db58e46-68a3-4ba0-a8aa-094893c045a1, storagePoolId =
 7ccd6ea9-7d80-4170-afa1-64c10c185aa6) execution failed. Exception:
 VDSErrorException: VDSGenericException: VDSErrorException: Failed to
 SpmStatusVDS, error = [Errno 30] Read-only file system, code = 100
 
 2014-12-17 19:57:13,363 INFO
 [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData]
 (DefaultQuartzScheduler_Worker-47) [4e9290a2] hostFromVds::selectedVds -
 U23.domainname.net, spmStatus returned null!
 
 
 
 
 
 According to Ovirt/Gluster, if a brick goes down, the VM should be able to be
 restarted from another brick without issue. This does not appear to be the
 case… If we take other bricks offline, it appears to work as expected.
 Something with this specific brick cases everything to break which then
 makes any VM’s that were running from the brick unable to start.
 
 ___
 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


Re: [ovirt-users] Cannot activate storage domain

2014-12-18 Thread Sahina Bose


On 12/18/2014 01:35 PM, Vered Volansky wrote:

Adding Sahina.

- Original Message -

From: Brent Hartzell brent.hartz...@outlook.com
To: users@ovirt.org
Sent: Thursday, December 18, 2014 3:38:11 AM
Subject: [ovirt-users] Cannot activate storage domain



Have the following:



6 hosts – virt + Gluster shared



Gluster volume is distributed-replicate – replica 2



Shutting down servers one at a time all work except for 1 brick. If we shut
down one specific brick (1 brick per host) – we’re unable to activate the
storage domain. VM’s that were actively running from other bricks continue
to run. Whatever was running form that specific brick fails to run, gets
paused etc.



Error log shows the entry below. I’m not certain what it’s saying is read
only…nothing is read only that I can find.





2014-12-17 19:57:13,362 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-47) [4e9290a2] Command
SpmStatusVDSCommand(HostName = U23.domainame.net, HostId =
0db58e46-68a3-4ba0-a8aa-094893c045a1, storagePoolId =
7ccd6ea9-7d80-4170-afa1-64c10c185aa6) execution failed. Exception:
VDSErrorException: VDSGenericException: VDSErrorException: Failed to
SpmStatusVDS, error = [Errno 30] Read-only file system, code = 100

2014-12-17 19:57:13,363 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData]
(DefaultQuartzScheduler_Worker-47) [4e9290a2] hostFromVds::selectedVds -
U23.domainname.net, spmStatus returned null!





According to Ovirt/Gluster, if a brick goes down, the VM should be able to be
restarted from another brick without issue. This does not appear to be the
case… If we take other bricks offline, it appears to work as expected.
Something with this specific brick cases everything to break which then
makes any VM’s that were running from the brick unable to start.


Do you have the recommended options for using volume as virt store 
turned on? Is client-side quorum turned on for the volume? Is the brick 
that causes the issue, the first brick in the replica set?





___
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


Re: [ovirt-users] Cannot activate storage domain

2014-12-18 Thread Sahina Bose

[+Sas - thanks for the link to virt-store usecase article inline]

On 12/18/2014 06:56 PM, Brent Hartzell wrote:

Hello,

I had actually gotten this sorted out, somewhat. If I disable server quorum
on the volume, the storage domain will activate. The volume is/was optimized
for virt store via oVirt. The brick in question was not the first brick
added to the volume through oVirt however, it appears that it may have been
the first brick in the replica being used, but I'm not certain how to find
this out.


The recommended setting is to have both client and server side quorum 
turned on. But turning on server-side quorum with a 2-way replica volume 
would mean that your volume goes offline when one of the bricks goes down.


gluster volume info command will give you information about the volume 
topology. So will the bricks sub-tab for Volume in oVirt. The order in 
which the bricks are listed, is the order of the replica sets.



Disabling quorum allowed me to get the VM's affected back online however, is
this the recommended procedure? I tried to use replace-brick with another
node but it failed because the failed brick was not available. Would we
leave quorum disabled until that brick gets replaced? IE - rebuild the
server with the same hostname/IP file structure and rebalance the cluster?


http://www.gluster.org/community/documentation/index.php/Virt-store-usecase 
- for recommendations on volume tunables.


You could add another brick to your volume to make it a replica 3 and 
then turn on quorum?


For help on recovering your volume, I suggest you write to 
gluster-us...@gluster.org







While that happened, I read somewhere about this happening with a replica 2
- I've created a new volume with replica 3 and plan to test this again. Is
there any info you can point me to for how to handle this when it happens or
what the correct procedure is when a first brick fails?






-Original Message-
From: Sahina Bose [mailto:sab...@redhat.com]
Sent: Thursday, December 18, 2014 3:51 AM
To: Vered Volansky; Brent Hartzell
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Cannot activate storage domain


On 12/18/2014 01:35 PM, Vered Volansky wrote:

Adding Sahina.

- Original Message -

From: Brent Hartzell brent.hartz...@outlook.com
To: users@ovirt.org
Sent: Thursday, December 18, 2014 3:38:11 AM
Subject: [ovirt-users] Cannot activate storage domain



Have the following:



6 hosts - virt + Gluster shared



Gluster volume is distributed-replicate - replica 2



Shutting down servers one at a time all work except for 1 brick. If
we shut down one specific brick (1 brick per host) - we're unable to
activate the storage domain. VM's that were actively running from
other bricks continue to run. Whatever was running form that specific
brick fails to run, gets paused etc.



Error log shows the entry below. I'm not certain what it's saying is
read only.nothing is read only that I can find.





2014-12-17 19:57:13,362 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-47) [4e9290a2] Command
SpmStatusVDSCommand(HostName = U23.domainame.net, HostId =
0db58e46-68a3-4ba0-a8aa-094893c045a1, storagePoolId =
7ccd6ea9-7d80-4170-afa1-64c10c185aa6) execution failed. Exception:
VDSErrorException: VDSGenericException: VDSErrorException: Failed to
SpmStatusVDS, error = [Errno 30] Read-only file system, code = 100

2014-12-17 19:57:13,363 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData]
(DefaultQuartzScheduler_Worker-47) [4e9290a2]
hostFromVds::selectedVds - U23.domainname.net, spmStatus returned null!





According to Ovirt/Gluster, if a brick goes down, the VM should be
able to be restarted from another brick without issue. This does not
appear to be the case. If we take other bricks offline, it appears to

work as expected.

Something with this specific brick cases everything to break which
then makes any VM's that were running from the brick unable to start.

Do you have the recommended options for using volume as virt store turned
on? Is client-side quorum turned on for the volume? Is the brick that causes
the issue, the first brick in the replica set?



___
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] Cannot activate storage domain

2014-12-17 Thread Brent Hartzell
Have the following:

 

6 hosts - virt + Gluster shared

 

Gluster volume is distributed-replicate - replica 2

 

Shutting down servers one at a time all work except for 1 brick. If we shut
down one specific brick (1 brick per host) - we're unable to activate the
storage domain. VM's that were actively running from other bricks continue
to run. Whatever was running form that specific brick fails to run, gets
paused etc. 

 

Error log shows the entry below. I'm not certain what it's saying is read
only.nothing is read only that I can find.  

 

 

2014-12-17 19:57:13,362 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-47) [4e9290a2] Command
SpmStatusVDSCommand(HostName = U23.domainame.net, HostId =
0db58e46-68a3-4ba0-a8aa-094893c045a1, storagePoolId =
7ccd6ea9-7d80-4170-afa1-64c10c185aa6) execution failed. Exception:
VDSErrorException: VDSGenericException: VDSErrorException: Failed to
SpmStatusVDS, error = [Errno 30] Read-only file system, code = 100

2014-12-17 19:57:13,363 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData]
(DefaultQuartzScheduler_Worker-47) [4e9290a2] hostFromVds::selectedVds -
U23.domainname.net, spmStatus returned null!

 

 

According to Ovirt/Gluster, if a brick goes down, the VM should be able to
be restarted from another brick without issue. This does not appear to be
the case. If we take other bricks offline, it appears to work as expected.
Something with this specific brick cases everything to break which then
makes any VM's that were running from the brick unable to start.

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