From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Christian Holtje <docwhat@gmail.com>, git@vger.kernel.org
Subject: Re: pread() over NFS (again) [1.5.5.4]
Date: Thu, 26 Jun 2008 15:04:25 -0700 [thread overview]
Message-ID: <7vod5nq2dy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080626210556.GZ11793@spearce.org> (Shawn O. Pearce's message of "Thu, 26 Jun 2008 17:05:56 -0400")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> We have a file position we saw once before as the start of a delta.
> We wrote it down to disk. We want to go back and open it up, as
> we have the base decompressed and in memory and need to compute
> the SHA-1 of the object that resides at this offset.
>
> And *wham* we get an EOF. Where there should be data. Where we
> know there is data.
We have written that earlier in the same process? Are we playing games
with mixed mmap() and pread()? Is fsync() or msync() or unmap/remap
needed?
> Actually, I think the last time someone reported something like this
> in Git it turned out to be an NFS kernel bug. I didn't quote it
> in my reply to him, but I think he did say this was a linux client,
> linux server.
This is getting into the area Linus would immediately know the answer to,
but he is away for this week.
next prev parent reply other threads:[~2008-06-26 22:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 16:40 pread() over NFS (again) [1.5.5.4] Christian Holtje
2008-06-26 20:46 ` Shawn O. Pearce
2008-06-26 20:56 ` Junio C Hamano
2008-06-26 21:05 ` Shawn O. Pearce
2008-06-26 21:36 ` Christian Holtje
2008-06-26 22:04 ` Junio C Hamano [this message]
2008-06-26 22:07 ` Shawn O. Pearce
2008-06-26 23:36 ` logank
2008-06-26 23:38 ` Junio C Hamano
2008-06-27 2:57 ` J. Bruce Fields
2008-06-27 14:50 ` Trond Myklebust
2008-06-30 0:32 ` Shawn O. Pearce
2008-06-30 19:09 ` Nicolas Pitre
2008-06-27 2:54 ` J. Bruce Fields
2008-06-27 13:44 ` Christian Holtje
2008-06-27 13:54 ` Christian Holtje
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=7vod5nq2dy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=docwhat@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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.