Did anyone encount this problem when excute "git pull", this output is :
[zzp@42 gluster]$ git pull
ssh_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
.com>:
> On Wed, Apr 05, 2017 at 09:18:39AM +0800, Zhengping Zhou wrote:
>> I have a test environment without internet connection. I'd like
>> to build and install many packages from the tarball which downloaded
>> from the official website.
>> Generally, the ta
I have encountered a problem while trying to compile the
release source tarball as usual :./confiugre;make;make install.
It seems the Makefile generated by configure is not right and
without any obvious error message.(Actually there are several
warnings, such like "configure: WARNING: cache
Hi all:
Seem's something is wrong on the website
https://download.gluster.org/pub/gluster/glusterfs/3.8/LATEST/; The
sha256sum file should be 3.8.10.sha256sum.
Maybe someone could fix it.
Thanks
Zhengping
___
Gluster-devel mailing list
.@redhat.com>:
>
>
> - Original Message -----
>> From: "Zhengping Zhou" <johnzzpcrys...@gmail.com>
>> To: gluster-devel@gluster.org
>> Sent: Tuesday, July 12, 2016 9:28:01 AM
>> Subject: [Gluster-devel] [puzzle] readv operation allocate iobuf twice
>>
&
I have all ready filed a bug with bugid 1354205, but my current patch
still has problem in my test environment, I'll check it out and post
later.
2016-07-12 12:38 GMT+08:00 Raghavendra Gowdappa <rgowd...@redhat.com>:
>
>
> - Original Message -
>> From: "Zh
Hi all:
It is a puzzle to me that we allocate rsp buffers for rspond
content in function client3_3_readv, but these rsp parameters hasn't
ever been saved to struct saved_frame in submit procedure. Which means
the iobuf will reallocated by transport layer in function
Hello all:
I have submitted some patch to glusterfs through gerrit , but there
always are spurious regression test errors. I am wondering what to do when
there is no relevant error message around this patch in Jenkins console's
output. It seems I only have two choice.
First is just
