From: Alex Riesen <raa.lkml@gmail.com>
To: Bill Lear <rael@zopyra.com>
Cc: git@vger.kernel.org, nfs@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: git 1.5.3.5 error over NFS
Date: Tue, 13 Nov 2007 00:31:03 +0100 [thread overview]
Message-ID: <20071112233103.GH2918@steel.home> (raw)
In-Reply-To: <18232.29603.856766.275854@lisa.zopyra.com>
Bill Lear, Mon, Nov 12, 2007 16:39:15 +0100:
> On Saturday, November 10, 2007 at 00:21:06 (+0100) Alex Riesen writes:
> >Bill Lear, Fri, Nov 09, 2007 16:31:39 +0100:
> >> I've brought this up before, but I don't recall a resolution to it.
> >>
> >> We have an NFS-mounted filesystem, and git pull is choking on it.
> >>
> >> % uname -a
> >> Linux uhlr.zopyra.com 2.6.9-42.0.2.ELsmp #1 SMP Wed Aug 23 13:38:27 BST 2006 x86_64 x86_64 x86_64 GNU/Linux
It is a really old kernel... Maybe you could try with some of the
recent ones?
> >> % git --version
> >> git version 1.5.3.5
> >>
> >> % git pull
> >> remote: Generating pack...
> >> remote: Done counting 998 objects.
> >> remote: Result has 836 objects.
> >> remote: Deltifying 836 objects.
> >> remote: 100% (836/836) done
> >> Indexing 836 objects...
> >> remote: Total 836 (delta 526), reused 688 (delta 380)
> >> 100% (836/836) done
> >> Resolving 526 deltas...
> >> fatal: cannot pread pack file: No such file or directory
> >
> >Could you please strace it? With strace -ff?
> >
> >> fatal: index-pack died with error code 128
> >> fatal: Fetch failure: git://source/repo
> >>
> >> I looked through the archives of this list and did not see a final
> >> resolution, other than a suspected bug in the OS NFS code.
> >
> >Strace, just to be on the safe side
>
> Ok, I've done the strace -ff. It has generated 176 strace.out.<pid>
> files. I have placed a tarball of these files on my home server:
>
> http://www.zopyra.com/~rael/git/git-trace.tar.bz2
>
> The file strace.out.25526 has, at the very end:
>
Yes, this is the file.
I extend the part you quoted. The file is opened here:
open(".git/objects/pack_awOTNW", O_RDWR|O_CREAT|O_EXCL, 0600) = 3
write(3, "PACK\0\0\0\2\0\0\3r", 12) = 12
... lots of data. Counted writes: 488538...
write(3, "v\351\247V\325\362\327/\240\265\211\211\322,\261\210\301"..., 4096) = 4096
write(3, "\202\202g\232Bf\211Bf\261Bb\36X\22\4\364\365\25\22\223"..., 1114) = 1114
write(3, "M", 1) = 1
> write(2, "Resolving 551 deltas.\n", 22) = 22
> pread64(3, "", 242, 541) = 0
That's the problem. Hmm... May I kindly suggest moving the topic to
linux-nfs (cc-ed along with lk)?
next prev parent reply other threads:[~2007-11-12 23:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 15:31 git 1.5.3.5 error over NFS Bill Lear
2007-11-09 23:21 ` Alex Riesen
2007-11-12 15:39 ` Bill Lear
2007-11-12 23:31 ` Alex Riesen [this message]
2007-11-12 23:33 ` Alex Riesen
2007-11-13 14:49 ` Bill Lear
2007-11-13 21:48 ` git 1.5.3.5 error over NFS (pack data corruption) Alex Riesen
2007-11-13 23:56 ` Bill Lear
2007-11-14 0:02 ` Alex Riesen
2007-11-14 0:11 ` Bill Lear
2007-11-14 19:54 ` Alex Riesen
2007-11-14 1:28 ` Nicolas Pitre
2007-11-14 1:32 ` Junio C Hamano
2007-11-14 1:38 ` git 1.5.3.5 error over NFS Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071112233103.GH2918@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=rael@zopyra.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).