Odd remote: error: packfile ./objects/pack/pack-FOO.pack cannot be accessed

I have a simple post-receive hook as follows :

#!/bin/bash # using bash and not simple sh # simply checkout the master branch to notBare path, use tools from that portion to deploy further notBareRepo='/home/sudhi/repo/notBare/myproj-master' GIT_WORK_TREE="$notBareRepo" git reset --hard master #end post-receive

But when I push, I get this odd error from remote

$ git push --verbose --mirror
ssh://wadkar@192.168.1.177:7185/~wadkar/repo/bare/myproj.git
Pushing to ssh://wadkar@192.168.1.177:7185/~wadkar/repo/bare/myproj.git
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 323 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: error: packfile
./objects/pack/pack-17900952dc824651db15369a341eec8d3e8f39d2.pack
cannot be accessed
remote: HEAD is now at 4d5a6f1 Investigate and report odd error
To ssh://wadkar@192.168.1.177:7185/~wadkar/repo/bare/myproj.git
   d066a2f..4d5a6f1  master -> master

This happens even if I do a fresh clone on remote server as:

$ cd repo/bare; git clone --mirror wadkar@my_ip_address:myproj

Local " git fsck " reports few dangling blobs but nothing fancy/serious. Remote git version is 1.7.4.1 on a CentOS 5.7, while the local is same (1.7.4.1) on a Ubuntu 11.04.

1. How bad is the situation?
2. Have I done something wrong, or this is not my doing?
3. The checked out version in repo/notBare is fine, and seems to be
working (I can pass my unit-tests). Should I be worried?
4. If not, then can I ignore this particular error and move on?

-Sudarshan Wadkar

"Success is getting what you want. Happiness is wanting what you get."
- Dale Carnegie
"It's always our decision who we are"
- Robert Solomon in Waking Life
"The truth is the truth, so all you can do is live with it."
--Systematic Chaos