[Users] Ovirt 3.3.2 Cannot attach POSIX (gluster) storage domain

[Steve Dainard]

Hi Nir,

Do you need any more info from me? I missed the 'sanlock client host_status
-D' request, info below:

[root at ovirt002 ~]# sanlock client host_status -D
lockspace a52938f7-2cf4-4771-acb2-0c78d14999e5
1 timestamp 0
    last_check=176740
    last_live=205
    last_req=0
    owner_id=1
    owner_generation=5
    timestamp=0
    io_timeout=10
2 timestamp 176719
    last_check=176740
    last_live=176740
    last_req=0
    owner_id=2
    owner_generation=7
    timestamp=176719
    io_timeout=10
250 timestamp 0
    last_check=176740
    last_live=205
    last_req=0
    owner_id=250
    owner_generation=1
    timestamp=0
    io_timeout=10

[root at ovirt001 ~]# sanlock client host_status -D
[root at ovirt001 ~]#


*Steve Dainard *
IT Infrastructure Manager
Miovision <http://miovision.com/> | *Rethink Traffic*
519-513-2407 ex.250
877-646-8476 (toll-free)

*Blog <http://miovision.com/blog>  |  **LinkedIn
<https://www.linkedin.com/company/miovision-technologies>  |  Twitter
<https://twitter.com/miovision>  |  Facebook
<https://www.facebook.com/miovision>*
------------------------------
 Miovision Technologies Inc. | 148 Manitou Drive, Suite 101, Kitchener, ON,
Canada | N2C 1L3
This e-mail may contain information that is privileged or confidential. If
you are not the intended recipient, please delete the e-mail and any
attachments and notify us immediately.


On Wed, Feb 5, 2014 at 1:39 PM, Steve Dainard <sdainard at miovision.com>wrote:

>
>
> *Steve Dainard *
> IT Infrastructure Manager
> Miovision <http://miovision.com/> | *Rethink Traffic*
> 519-513-2407 ex.250
> 877-646-8476 (toll-free)
>
> *Blog <http://miovision.com/blog>  |  **LinkedIn
> <https://www.linkedin.com/company/miovision-technologies>  |  Twitter
> <https://twitter.com/miovision>  |  Facebook
> <https://www.facebook.com/miovision>*
> ------------------------------
>  Miovision Technologies Inc. | 148 Manitou Drive, Suite 101, Kitchener,
> ON, Canada | N2C 1L3
> This e-mail may contain information that is privileged or confidential. If
> you are not the intended recipient, please delete the e-mail and any
> attachments and notify us immediately.
>
>
> On Wed, Feb 5, 2014 at 10:50 AM, Steve Dainard <sdainard at miovision.com>wrote:
>
>> On Tue, Feb 4, 2014 at 6:23 PM, Nir Soffer <nsoffer at redhat.com> wrote:
>>
>>> ----- Original Message -----
>>> > From: "Steve Dainard" <sdainard at miovision.com>
>>> > To: "Nir Soffer" <nsoffer at redhat.com>
>>> > Cc: "Elad Ben Aharon" <ebenahar at redhat.com>, "users" <users at ovirt.org>,
>>> "Aharon Canan" <acanan at redhat.com>
>>> > Sent: Tuesday, February 4, 2014 10:50:02 PM
>>> > Subject: Re: [Users] Ovirt 3.3.2 Cannot attach POSIX (gluster) storage
>>> domain
>>> >
>>> > Happens every time I try to add a POSIX SD type glusterfs.
>>> >
>>> > Logs attached.
>>>
>>> Hi Steve,
>>>
>>> I'm afraid we need more history in the logs. I want to see the logs from
>>> the time the machine started,
>>> until the time of the first error.
>>>
>>
>> No problem. I've rebooted both hosts (manager is installed on host
>> ovirt001). And I've attached all the logs. Note that I put the wrong DNS
>> name 'gluster-rr:/rep2' the first time I created the domain, hence the
>> errors. The POSIX domain created is against 'gluster-store-vip:/rep2'
>>
>> Note only host ovirt002 is in the POSIX SD cluster.
>>
>
> Sorry this is wrong, it should be ovirt001 is the only host in the POSIX
> SD cluster.
>
>
>>
>> I've also included the glusterfs log for rep2, with these errors:
>>
>> [2014-02-05 15:36:28.246203] W
>> [client-rpc-fops.c:873:client3_3_writev_cbk] 0-rep2-client-0: remote
>> operation failed: Invalid argument
>> [2014-02-05 15:36:28.246418] W
>> [client-rpc-fops.c:873:client3_3_writev_cbk] 0-rep2-client-1: remote
>> operation failed: Invalid argument
>> [2014-02-05 15:36:28.246450] W [fuse-bridge.c:2167:fuse_writev_cbk]
>> 0-glusterfs-fuse: 163: WRITE => -1 (Invalid argument)
>>
>>
>>>
>>> We suspect that acquireHostId fails because someone else has aquired the
>>> same id. We may see evidence
>>> in the logs.
>>>
>>> Also can you send the output of this command on the host that fails, and
>>> if you have other hosts using the
>>> same storage, also on some of these hosts.
>>>
>>>     sanlock client host_status -D
>>>
>>> And finally, can you attach also /var/log/sanlock.log?
>>>
>>> Thanks,
>>> Nir
>>>
>>>
>> Thanks,
>> Steve
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140207/799ed7a3/attachment-0001.html>