wbacks to using TCP instead of RDMA here? Thanks.
Regards,
Jon Heese
From: Mohammed Rafi K C <mailto:rkavu...@redhat.com>
Sent: Monday, March 23, 2015 3:29 AM
To: Jonathan Heese
Cc: gluster-users
Subject: Re: [Gluster-users] I/O error on replicated volume
On 03/23/2015 1
gt;>> [root@duke ~]# gluster volume info gluster_disk
>>>
>>> Volume Name: gluster_disk
>>> Type: Replicate
>>> Volume ID: 2307a5a8-641e-44f4-8eaf-7cc2b704aafd
>>> Status: Started
>>> Number of Bricks: 1 x 2 = 2
>>> Transport-type: tcp
>>&
ny (significant)
drawbacks to using TCP instead of RDMA here? Thanks.
Regards,
Jon Heese
From: Mohammed Rafi K C <mailto:rkavu...@redhat.com>
Sent: Monday, March 23, 2015 3:29 AM
To: Jonathan Heese
Cc: gluster-users
Subject: Re: [Gluster-users] I/O err
CP connections are going
> over the InfiniBand connections between the two Gluster servers (based
> on the hostnames which are pointed to the IB IPs via hosts files), are
> there any (significant) drawbacks to using TCP instead of RDMA here?
> Thanks.
>
>
> Regards,
>
&
>
<mailto:gluster-users-boun...@gluster.org>
on behalf of Joe Julian <mailto:j...@julianfamily.org>
Sent: Thursday, March 26, 2015 4:08 PM
To: gluster-users@gluster.org<mailto:gluster-users@gluster.org>
Subject: Re: [Gluster-users] I/O error on replicated volume
The RDMA warn
*From:* gluster-users-boun...@gluster.org
on behalf of Joe Julian
*Sent:* Thursday, March 26, 2015 4:08 PM
*To:* gluster-users@gluster.org
*Subject:* Re: [Gluster-users] I/O error on replicated volume
The RDMA warnings are not relevant if you don't use RDMA. It
March 26, 2015 4:08 PM
To: gluster-users@gluster.org<mailto:gluster-users@gluster.org>
Subject: Re: [Gluster-users] I/O error on replicated volume
The RDMA warnings are not relevant if you don't use RDMA. It's simply pointing
out that it tried to register and it couldn't, which w
nt:* Thursday, March 26, 2015 4:08 PM
*To:* gluster-users@gluster.org
*Subject:* Re: [Gluster-users] I/O error on replicated volume
The RDMA warnings are not relevant if you don't use RDMA. It's simply
pointing out that it tried to register and it couldn't, which would be
expecte
Regards,
Jon Heese
From: gluster-users-boun...@gluster.org on
behalf of Joe Julian
Sent: Thursday, March 26, 2015 4:08 PM
To: gluster-users@gluster.org
Subject: Re: [Gluster-users] I/O error on replicated volume
The RDMA warnings are not relevant if you don
rors in the testing I've done so far.
Thanks.
Regards,
Jon Heese
*From:* gluster-users-boun...@gluster.org
on behalf of Jonathan Heese
*Sent:* Friday, March 20, 2015 7:04 AM
*To:* Mohammed Rafi K C
*Cc:* gluster-users
*Subject:
nks.
Regards,
Jon Heese
From: Mohammed Rafi K C
Sent: Monday, March 23, 2015 3:29 AM
To: Jonathan Heese
Cc: gluster-users
Subject: Re: [Gluster-users] I/O error on replicated volume
On 03/23/2015 11:28 AM, Jonathan Heese wrote:
On Mar 23, 2015, at 1:20 AM
f possible, can you paste the
>> volfile for nfs server. You can find the volfile in
>> /var/lib/glusterd/nfs/nfs-server.vol or
>> /usr/local/var/lib/glusterd/nfs/nfs-server.vol
>
> I will get this for you when I can. Thanks.
If you can make it, that will be great help t
gluster.org<mailto:gluster-users-boun...@gluster.org>
<mailto:gluster-users-boun...@gluster.org>
on behalf of Jonathan Heese <mailto:jhe...@inetu.net>
Sent: Friday, March 20, 2015 7:04 AM
To: Mohammed Rafi K C
Cc: gluster-users
Subject: Re: [Gluster-users] I/O error on replicated v
>
> Regards,
>
> Jon Heese
>
>
> ------------------------
> *From:* gluster-users-boun...@gluster.org
> on behalf of Jonathan Heese
>
> *Sent:* Friday, March 20, 2015 7:04 AM
> *To:* Mohammed Rafi K C
> *Cc:*
m: gluster-users-boun...@gluster.org on
behalf of Jonathan Heese
Sent: Friday, March 20, 2015 7:04 AM
To: Mohammed Rafi K C
Cc: gluster-users
Subject: Re: [Gluster-users] I/O error on replicated volume
Mohammed,
Thanks very much for the reply. I will try that and report back.
Regards,
Jon Heese
On
t: Tuesday, March 17, 2015 12:36 PM
To: 'Ravishankar N'; gluster-users@gluster.org<mailto:gluster-users@gluster.org>
Subject: RE: [Gluster-users] I/O error on replicated volume
Ravi,
The last lines in the mount log before the massive vomit of I/O errors are from
22 minutes prior, and seem
ng*
> P: 610.266.7441 x 261
> F: 610.266.7434
> www.inetu.net <https://www.inetu.net/>
>
> /** This message contains confidential information, which also may be
> privileged, and is intended only for the person(s) addressed above.
> Any unauthorized use, distribution, copying or disc
ication in error, please erase all copies of the message and its
attachments and notify the sender immediately via reply e-mail. **
From: Jonathan Heese
Sent: Tuesday, March 17, 2015 12:36 PM
To: 'Ravishankar N'; gluster-users@gluster.org
Subject: RE: [Gluster-users] I/O error on replicate
l and/or
privileged information is strictly prohibited. If you have received this
communication in error, please erase all copies of the message and its
attachments and notify the sender immediately via reply e-mail. **
From: Ravishankar N [mailto:ravishan...@redhat.com]
Sent: Tuesday, March 17
On 03/17/2015 02:14 AM, Jonathan Heese wrote:
Hello,
So I resolved my previous issue with split-brains and the lack of
self-healing by dropping my installed glusterfs* packages from 3.6.2
to 3.5.3, but now I've picked up a new issue, which actually makes
normal use of the volume practically
Hello,
So I resolved my previous issue with split-brains and the lack of self-healing
by dropping my installed glusterfs* packages from 3.6.2 to 3.5.3, but now I've
picked up a new issue, which actually makes normal use of the volume
practically impossible.
A little background for those not al
21 matches
Mail list logo