Re: Error "fatal: cannot pread pack file: Success"

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Feb 28, 2007, 17:13 UTC
Message-ID: <Pine.LNX.4.64.0702280910330.12485@woody.linux-foundation.org>
In-Reply-To: <17893.45903.748382.298137@lisa.zopyra.com>

On Wed, 28 Feb 2007, Bill Lear wrote:

Show 6 quoted lines

> >
> >Getting 305 bytes back when you asked for 207 is a bad bad bad thing. It's 
> >also really really odd and unexpected. 
> 
> You may have missed my admission that I screwed up the print: n is 0, obj->size
> was 305.

Ahh, ok.

That means you got 0 back. That in turn means that the file seems to be truncated for some reason - the only valid reason to get 0 back is if the length of the file is smaller than the offset you're asking for data from.

Show 7 quoted lines

> >What filesystem? And could you strace this and actually see the pread() 
> >system call?
> 
> How can I tell which filesystem?  It's Linux all around, as far as I
> know.  Here is what mount tells me about this filesystem:
> 
> storage:/storage/disk1 on /austin type nfs (rw,addr=192.168.2.192)

Yes, that's how you get the filesystem type ;)

> >(use "strace -f -o tracefile" to follow all forks and to put the end 
> >result in a trace file)
> 
> Will do ...

Well, if the return value was 0, it wasn't as odd any more, and the reason seems to be a file truncate error. Shawn seems to be on that one.

(The "return 305 when asked for 207" seemed like a kernel bug, which was why I got really interested ;)

		Linus