git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [remote rejected] master -> master (n/a (unpacker error))

From
DDavidLeeCrites <lee@critesclan.com>
Date
Nov 27, 2015, 21:37 UTC
Message-ID
<1448660253143-7643470.post@n2.nabble.com>
In-Reply-To
<20100513005218.GA20655@progeny.tock>

I am getting the same kinds of errors, but the resolutions offered here did not work. After using the ideas (that there was a tmp_* file I did not have perms to write to, I started doing some global searches.

One such was this (from inside .git/objects): # ls -alR | grep tmp ls: reading directory ./97: Input/output error

So I tried: # cd 97 # ls -l ls: reading directory .: Input/output error total 0K

To fix it, I did this: # cd .. # rm -fr ./97

The git push then worked fine.

I'll add a few more pieces to the puzzle. I have some of my git repositories on a USB drive (the ones I get this issue with). I move it from system to system. When git works, it works okay. But this irritant hits me about once a week. My previous solution was to blow away the repo and rebuild it (something suggested several times here). This is the first time I have found a workaround.

These are my private repositories that hold my private files. I have a github account I use for my public ones, plus my company has both a public github and their own privately hosted github. So the same exact computer systems (laptops and VMs) use all four with impunity. Almost all of them are linux based -- a mix of CentOS 7.x and Linux Mint 14.x; all using git v1.9.1. The one exception is osx. Thus the (brand new Toshiba 4T) USB drive is built with the exFAT filesystem. When it works, it works okay; but as I said, one of my dozen git repos will fail like this on a weekly basis.

None of the items in my dockerhub or artifactory fail, nor do my rsnapshot processes, or VLC/Banshee, etc.

I've pretty much isolated it down to git. It is the ONLY app that fails. I have noted in the past few months that the frequency of errors tells me I cannot be using the USB drive for anything else while git is accessing the drive. [mac specific: it is better when I use a USB 2.0 hub to plug the drive in; we all are probably aware that the mac seems to have more issues with USB 3.0...]

Anyway, I figured I'd toss this into the mix. Since it only happens once a week or so, I cannot guarantee I'll have an update soon, but if someone is curious, ping me, and I'll let you know when it happens again.

DL

-- View this message in context: http://git.661346.n2.nabble.com/remote-rejected-master-master-n-a-unpacker-error-tp5043046p7643470.html Sent from the git mailing list archive at Nabble.com.

Previous: Jonathan Nieder
Message 8 of 8 in “[remote rejected] master -> master (n/a (unpacker error))”
  1. Robert BuckMay 12, 2010
  2. Chris PackhamMay 13, 2010
  3. Jonathan NiederMay 13, 2010
  4. Robert BuckMay 13, 2010
  5. Greg TroxelMay 13, 2010
  6. Andreas SchwabMay 13, 2010
  7. Jonathan NiederMay 13, 2010
  8. DavidLeeCritesNov 27, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.