Problem with Posix Compliant FS -- Host in non-operational state

Monday, 18 August 2014

This is a multi-part message in MIME format.
--------------000807020601060107070501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I have a home lab in which I am learning about oVirt, but I'm having 
some trouble and thought some kind souls out there could point me in the 
right direction.

There are two servers, each server in it's own cluster (long story, but 
that's how it is). I'm on oVirt 3.4.x on both hosts, and the hosts are 
running CentOS 6.5. A third machine is acting as the engine, so nothing 
too funky there -- it too is running CentOS 6.5. I created a Posix 
Compliant FS on one of the hosts (hostB). It is a LVM device where I 
carved out 100GB from an existing volume group. The storage worked 
great, I moved an imported server there and it runs beautifully. 
However... the other host (hostA) is now in a "non-operational" state 
because it can't get to the LVM device of hostB. Since it's a local 
device on hostB, I am not surprised that hostA can't get to it; 
nevertheless, hostA thinks it is in a bad state and every minute tries 
to migrate the guests it is hosting off to another host (except there 
are no other hosts because I don't have the hardware yet).

Also hostB has somehow become the SPM -- but I'd prefer hostA to be the 
SPM; it has better connectivity.

So.. questions:
1) I read on the Internet somehwhere that this could be a caching issue 
and that restarting the host could fix it. Any thoughts on that?
2) Is there something I should do to make the Posix Compliant FS 
accessible to hostA?
3) Would removing the Posix Compliant FS bring hostA back into happiness 
without a reboot?
4) How do I force hostA to be the SPM or revoke hostB's SPM status?

Thanks for your time and help!

-Eric

--------------000807020601060107070501
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html><head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1"></head><body
 bgcolor="#FFFFFF" text="#000000">
  <span>I have a home lab in which I am learning about oVirt, but I'm 
having 
some trouble and thought some kind souls out there could point me in the

right direction.
<br>
<br>There are two servers, each server in it's own cluster (long story, 
but 
that's how it is). I'm on oVirt 3.4.x on both hosts, and the hosts are 
running CentOS <span 
__postbox-detected-content="__postbox-detected-date" 
class="__postbox-detected-content __postbox-detected-date" 
style="display: inline; font-size: inherit; padding: 0pt;"><span 
__postbox-detected-content="__postbox-detected-date" 
class="__postbox-detected-content __postbox-detected-date" 
style="display: inline; font-size: inherit; padding:
0pt;">6.5.</span></span>
 A third machine is acting as the engine, so nothing 
too funky there -- it too is running CentOS <span 
__postbox-detected-content="__postbox-detected-date" 
class="__postbox-detected-content __postbox-detected-date" 
style="display: inline; font-size: inherit; padding: 0pt;">6.5.</span>
I
 created a Posix 
Compliant FS on one of the hosts (hostB). It is a LVM device where I 
carved out 100GB from an existing volume group. The storage worked 
great, I moved an imported server there and it runs beautifully. 
However... the other host (hostA) is now in a "non-operational" state 
because it can't get to the LVM device of hostB. Since it's a local 
device on hostB, I am not surprised that hostA can't get to it; 
nevertheless, hostA thinks it is in a bad state and every minute tries 
to migrate the guests it is hosting off to another host (except there 
are no other hosts because I don't have the hardware yet).
<br>
<br>Also hostB has somehow become the SPM -- but I'd prefer hostA to be 
the 
SPM; it has better connectivity.
<br>
<br>So.. questions:
<br>1) I read on the Internet somehwhere that this could be a caching 
issue 
and that restarting the host could fix it. Any thoughts on that?
<br>2) Is there something I should do to make the Posix Compliant FS 
accessible to hostA?
<br>3) Would removing the Posix Compliant FS bring hostA back into 
happiness 
without a reboot?
<br>4) How do I force hostA to be the SPM or revoke hostB's SPM status?
<br>
<br>Thanks for your time and help!
<br>
<br>-Eric
<br>
<br>
<br>
<br>
<br>&nbsp;
    <br>
  </span>
</body>
</html>

--------------000807020601060107070501--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011