From: Junio C Hamano <gitster@pobox.com>
To: Lars Winterfeld <lars.winterfeld@tu-ilmenau.de>
Cc: <git@vger.kernel.org>
Subject: Re: bug: "fatal: cannot pread pack file", version 1.7.5.4
Date: Mon, 02 Jul 2012 14:45:02 -0700 [thread overview]
Message-ID: <7v3959zvkx.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5638dec6e156f83385a3baa01cf9ac4d@localhost> (Lars Winterfeld's message of "Mon, 02 Jul 2012 12:03:13 -0700")
Lars Winterfeld <lars.winterfeld@tu-ilmenau.de> writes:
> Hi,
>
> I have used git for some time and regularly pushed changes to another
> server (as some kind of backup), but today I got this error during
> git push`:
>
> Counting objects: 1293, done.
> Compressing objects: 100% (1027/1027), done.
> Writing objects: 100% (1229/1229), 70.83 MiB | 364 KiB/s, done.
> Total 1229 (delta 343), reused 0 (delta 0)
> fatal: cannot pread pack file: No such file or directory
Curious. That is typically given for ENOENT but pread(2) would not
give that error according to
http://pubs.opengroup.org/onlinepubs/9699919799/functions/pread.html
You didn't say what platform you are seeing the issue (the receiving
end of the "push"), but are you using Git on a pread-deficient
platform with emulation perhaps?
next prev parent reply other threads:[~2012-07-02 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 19:03 bug: "fatal: cannot pread pack file", version 1.7.5.4 Lars Winterfeld
2012-07-02 21:45 ` Junio C Hamano [this message]
2012-07-02 21:57 ` Jeff King
2012-07-02 22:43 ` Andreas Schwab
2012-07-02 23:50 ` Junio C Hamano
2012-07-03 3:45 ` Jeff King
2012-07-03 4:25 ` Nguyen Thai Ngoc Duy
2012-07-03 5:14 ` Jeff King
2012-07-03 17:16 ` Junio C Hamano
2012-08-16 21:51 ` Junio C Hamano
2012-08-16 22:10 ` Lars Winterfeld
2012-08-16 23:05 ` Junio C Hamano
2012-08-16 23:36 ` Lars Winterfeld
2012-08-17 1:45 ` Jeff King
2012-08-17 3:02 ` Junio C Hamano
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=7v3959zvkx.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lars.winterfeld@tu-ilmenau.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.