On Mon, 25 Aug 2008, J. Bruce Fields wrote:
This is almost certainly due to some corruption. Basically, the call to
"cache_or_unpack_entry()" failed, which in turn is because
'unpack_entry()' will have failed.
And since you didn't see any other error, that failure is almost certainly
due to unpack_compressed_entry() having failed. We don't print out _why_
(which is a bit sad), but the only thing that unpack_compressed_entry()
does is to just "inflate()" the data at that offset.
So it probably got a zlib data error, or an adler32 crc failure.
> This has happened once before recently, I believe with a pack that had
An interrupted fetch shouldn't have caused this, it really should only
happen if you have some actual filesystem data error. Something didn't get
written back correctly, or the page cache isn't coherent (or it got
corrupted by something else like a wild kernel pointer, of course).
Linus
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Linus Torvalds | Linux 2.6.21-rc1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| pageexec | Re: [stable] Linux 2.6.25.10 |
| Linus Torvalds | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
git: | |
