Re: [Bug] vfat: Not a git archive
- From
- Stephen Sinclair <radarsat1@gmail.com>
- Date
- Jun 2, 2008, 15:16 UTC
- Message-ID
- <9b3e2dc20806020816r502de6bfjd704040d15858c82@mail.gmail.com>
- In-Reply-To
- <e1dab3980806020337x4d62dcablcf8d4385466b1b2f@mail.gmail.com>
On Mon, Jun 2, 2008 at 6:37 AM, David Tweed <david.tweed@gmail.com> wrote:
Show 23 quoted lines
> On Mon, Jun 2, 2008 at 11:20 AM, Thomas Christensen > <thomasc@thomaschristensen.org> wrote: >> Hi, >> >> I am having this issue on Debian with kernel 2.6.25 (2.6.24 works fine) >> and git 1.5.5.3. >> >> $ git push /media/KINGSTON/foo.git >> fatal: '/media/KINGSTON/foo.git': unable to chdir or not a git archive >> fatal: The remote end hung up unexpectedly >> >> A notable difference between these 2 kernels is this line: >> >> [ 62.575939] FAT: utf8 is not a recommended IO charset for FAT >> filesystems, filesystem will be case sensitive! >> >> which appears in 2.6.25. > > I don't remember if it gives this particular error message, but some > vfat mounting options cause the file 'HEAD' to appear to the > filesystem as 'head' which git doesn't like. (I don't think there any > other basic git files which have uppercase.)It's worth having a look > and see if that's happened.
I recently had some issue where I got this "Not a git archive" message. Turned out it was something stupid I had done during a failed filter-branch operation, related to deleting my refs. But the message "Not a git archive" wasn't very helpful. Finally I found that recreating my refs manually (using cat) did the trick. But it would have been nice to have a more specific error message along with "Not a git archive", like "HEAD points to refs/heads/master, but file .git/refs/heads/master not found."
Steve