1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #10014 resolved

Unable to create temporary file: No space left on device

Shane Farmer
created an issue

Repeat of issue #9970. Error when attempting to push to repo. remote: fatal: Unable to create temporary file: No space left on device

Comments (82)

  1. Sanjay B

    Just to add my voice: experienced the same right now - same repository was working fine yesterday (about 12 hours ago). Is this perhaps related to planned maintenance / downtime scheduled for this weekend?

  2. Igor Manjencic

    Happening to me also.

    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. Tsachi Shlidor

    Same here

    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
    
  4. mrangan

    In total it was broken for at least 13 hours. It did not happen for all repositories. Some of my repositories continued to work fine. But, some repositories gave this problem.

  5. Adam Lane

    A google search shows so many people having this issue consistently over time that this probably deserves a place on the status page http://status.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
    error: failed to push some refs to 'https://enalmada@bitbucket.org/enalmada/powerlanguage.git'
    
  6. Marco Craveiro

    same issue, just now:

    Counting objects: 4, done. Writing objects: 100% (4/4), 157.05 KiB | 0 bytes/s, done. Total 4 (delta 1), reused 0 (delta 0) remote: error: unable to create temporary file: No space left on device
    remote: fatal: failed to write object

    Private repo.

    Thanks for your help.

  7. Kaleb Elwert

    Hello,

    Firstly, we apologize for the delayed response. Over the weekend we had a known issue with storage, however no data has been lost. Normally this would be handled automatically but due to unforeseen circumstances it was not. This issue should now be fixed. If you have any further problems relating to this, please feel free to contact support@bitbucket.org.

    Thank you for your patience

  8. Mehdi Mehni

    It seems that issue is back I got this message after an git fetch :

    remote: Counting objects: 99, done.
    remote: Compressing objects: 100% (92/92), done.
    error: unable to create temporary file: No space left on device
    fatal: failed to write object
    fatal: unpack-objects failed
    
  9. Andrea Verde

    Hi, i'm having the same issue

    Counting objects: 37, done.
    Delta compression using up to 8 threads.
    Compressing objects: 100% (37/37), done.
    Writing objects: 100% (37/37), 4.58 KiB | 0 bytes/s, done.
    Total 37 (delta 25), 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
    
  10. Kaleb Elwert staff

    We have an automated system which deals with this which does its best to rebalance repositories between our storage nodes. It still appears to be working (I've confirmed this with our ops team). Most issues like this should clear up 15 to 30 minutes after seeing the error. If it lasts longer than that, I strongly urge you to open a support ticket by emailing support@bitbucket.org as we do not actively monitor issues which have already been closed.

  11. Log in to comment