[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62A0BBF9-A71A-4EA0-A01A-722C0E451A69@fb.com>
Date: Tue, 8 May 2018 18:37:41 +0000
From: Song Liu <songliubraving@...com>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
CC: Networking <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...com>
Subject: Re: Failed to clone net-next.git
> On May 8, 2018, at 11:06 AM, Konstantin Ryabitsev <konstantin@...uxfoundation.org> wrote:
>
> On 05/08/18 13:46, Song Liu wrote:
>> We are seeing the following error on multiple different systems while
>> cloning net-next tree.
>>
>> $ git clone https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
>> Cloning into 'net-next'...
>> remote: Counting objects: 6017287, done.
>> remote: Compressing objects: 100% (2458/2458), done.
>> fatal: The remote end hung up unexpectedly 1.00 GiB | 8.13 MiB/s
>> fatal: early EOF
>> fatal: index-pack failed
>>
>> It looks like the size of the data being fetched reached server side
>> limit of 1.00 GiB. So we probably need change server side configuration.
>> Could someone please look into it?
>
> It was probably due to a timeout value. Can you try it now, I've bumped
> it to a much larger number.
>
> Regards,
> --
> Konstantin Ryabitsev
> Director, IT Infrastructure Security
> The Linux Foundation
Thanks Konstantin. It works for me now.
By the way, I do need to increase http.postBuffer on the client side:
git config --global http.postBuffer "something > 1GiB"
Song
Powered by blists - more mailing lists