Issue #8121 resolved

unable to create temporary file: No space left on device

John Fuller
created an issue

unable to create temporary file: No space left on device

Looks like this has been posted here before. Can you take a look? Do you need more info from me?

Comments (123)

  1. kuzyakiev

    same problem

    Password for 'https://*****@bitbucket.org':
    remote: error: unable to create temporary file: No space left on device
    remote: fatal: failed to write object
    error: unpack failed: unpack-objects abnormal exit
    To https://kuzyakiev@bitbucket.org/*****/*****.git
    
     ! [remote rejected] ***** -> ***** (unpacker error)
    error: failed to push some refs to 'https://*****@bitbucket.org/*****/*****.git'
    
  2. Charlie Calvert

    Similar problem on push:

    Compressing objects: 100% (18/18), done.
    Writing objects: 100% (19/19), 7.42 KiB, done.
    Total 19 (delta 10), reused 0 (delta 0)
    remote: error: unable to create temporary file: No space left on device
    remote: fatal: failed to write object
    error: unpack failed: unpack-objects abnormal exit
    
  3. Anna Khabibullina

    I see it today, too ../

    $ git push origin
    Counting objects: 48, done.
    Delta compression using up to 4 threads.
    Compressing objects: 100% (6/6), done.
    Writing objects: 100% (6/6), 557 bytes | 0 bytes/s, done.
    Total 6 (delta 5), reused 0 (delta 0)
    remote: error: unable to create temporary file: No space left on device
    remote: fatal: failed to write object
    error: unpack failed: unpack-objects abnormal exit
    To https://user:pass@bitbucket.org/user/repo.git
     ! [remote rejected] branch -> branch (unpacker error)
    error: failed to push some refs to 'https://user:pass@bitbucket.org
    /user/repo.git'
    
  4. Walter Lorenzetti

    Same error Counting objects: 17, done. Delta compression using up to 4 threads. Compressing objects: 100% (8/8), done. Writing objects: 100% (9/9), 851 bytes | 0 bytes/s, done. Total 9 (delta 7), reused 3 (delta 1) remote: error: unable to create temporary file: No space left on device remote: fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To https://bitbucket.org/wlorenzetti/turisticgis.git ! [remote rejected] master -> master (unpacker error) error: failed to push some refs to 'https://bitbucket.org/wlorenzetti/turisticgis.git'

  5. Alexander Nevidimov

    Got same error.

    remote: error: unable to create temporary file: No space left on device
    remote: fatal: failed to write object
    error: unpack failed: unpack-objects abnormal exit
    To ssh://git@bitbucket.org/nevidimov/giftd.git
     ! [remote rejected] devel -> devel (unpacker error)
    error: failed to push some refs to 'ssh://git@bitbucket.org/nevidimov/giftd.git'
    
  6. Tomasz Trejderowski

    People, please be reasonable and don't add comments to a RESOLVED issue! How do you want your problem to be noticed? Start new issue instead. Resolved ones are most likely to be not monitored.

    There's a blog entry about migrating repositories' internal storage, which says, that some repositories might be off-line (read-only) for up to 30 minutes. Mine was locked (inaccessible with unable to create temporary file: No space left on device error) for about two hours, but now it is back, fully operational. So, I don't know, if this just lasted two hours instead of 30 minutes or if this is an unrelated coincidence?

    What I actually did, was to... push changes to another repository on BitBucket. Push went without any problems and immediately after that, I managed to push changes to the first repository, which was refusing it for past two hours. So, I'm not sure, if this is really a strange coincidence or did I made some kind push-through, which just purged all the way my traffic flows from my computer to Bitbucket.

    Yes, I understand, that this sounds like stupidity and chasing the ghosts! :] I'm just writing, what happens: I wasn't able to push to repository A until I pushed changes to repository B. Then both repositories gone back to normal.

  7. Martin Ambrus

    Tomasz, there are already tickets with this (see Oleg Abrazhaev comment) where I also commented with a link to this issue.

    It seems that people are coming here from StackOverflow's best answer which leads to this old post and they just post away over here (that's what I did at first, too).

    Just saying... :P

  8. MattDavey

    If customers are reaching out to you to report a problem, you should appreciate and graciously receive that feedback, regardless of how/where it was delivered to you. It sends a very bad message if well intentioned feedback is met with "sorry, you're doing it wrong".

  9. Tomasz Trejderowski

    Matt, I think, you're only partially true:

    1. Resolved issues have resolved flag to inform, that they might not be monitored. I don't know, like about you, but I inform all my customers and users, that they should rise a new issue for a new problem, not to stick comments to resolved issue (or at least re-open it, by changing status, if their access rights allows this). Notice, that Bitbucket hides all issues with resolved status by default.

    2. You're using a free service. If you are a paid customer, you can complain on whatever you want. As long as it is free (at least I use the free plan), I can either accept, what do I get or... start to pay! :]

    I agree with you, that this is kind of bad message. But sometimes, it is a good idea to try to think like these guys on the other side. Or, try to predict, how you would like to see it or work? For me, ignoring a resolved issue is obvious. It might not be that obvious for you. Both of us have right to look at this, like we like! :]

  10. MattDavey

    Tomasz Trejderowski I appreciate your point of view, in many situations you are correct. In this particular situation, many users and entering the error message into google - which takes them to a stack overflow question - which links directly here. Thus we have a recurring problem, and a single landing point where many of our customers come to give us feedback. This should be considered an opportunity, it's not always the case that you get a single focal point to engage with your customers and address an issue. Anyway I think we are getting off topic, but it's an interesting conversation :)

  11. Matthias Hild

    Problem persists for me.

    remote: error: unable to create temporary file: No space left on device remote: fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To git@bitbucket.org:XXX ! [remote rejected] master -> master (unpacker error) error: failed to push some refs to 'git@bitbucket.org:XXX'

  12. Michael Frauenholtz staff

    consultwebs Julius Schorzman todd_fisher

    This should be resolved now.

    We have an automated process to handle moving data from full storage segments, but it was not able to manage this particular storage segment due to a background infrastructure change taking place at the time it became full. This change was completed and the storage has been rebalanced in addition to the automated process again managing this storage segment.

  13. goyelakin

    I was getting this error also. The cause for me was the number of files I had to push up and the slow speed of my network connection. Make sure you have a steady internet connection, and that should resolve the issue.

  14. Log in to comment