From: Duy Nguyen <pclouds@gmail.com>
Date: Thu, 21 May 2015 14:31:41 GMT
Subject: Re: Troubleshoot clone issue to NFS.
Message-ID: <CACsJy8AMhEKe-eM7jvYcEx+7ZmfvdD+p1s4VYHjKuAwZsDWc-w@mail.gmail.com>
In-Reply-To: <7FAE15F0A93C0144AD8B5FBD584E1C5519758FC3@C111KXTEMBX51.ERF.thomson.com>

On Thu, May 21, 2015 at 8:13 PM,  <steve.norman@thomsonreuters.com> wrote:

> So there appears to be a change in 1.8.4.2 that made this issue appear for me.  Looking at the release notes the only thing that I can see that might be related could be:
>
> * When an object is not found after checking the packfiles and then
>    loose object directory, read_sha1_file() re-checks the packfiles to
>    prevent racing with a concurrent repacker; teach the same logic to
>    has_sha1_file().

That would be commit 45e8a74 (has_sha1_file: re-check pack directory
before giving up - 2013-08-30). Maybe you can try the version without
that commit to confirm. In case an object is not found pack directory
is re-read again, which might cause some increased load on nfs.
has_sha1_file() not finding the object should not happen often.. Maybe
you could do an strace (following forks) on the "git clone" process to
see if readdir() is really called a lot?
-- 
Duy