Fatal Write Error Bad File Descriptor
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business bitbucket fatal: write error: bad file descriptor Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation
Git Fatal: Unable To Read
Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like
Git Object File Is Empty
you, helping each other. Join them; it only takes a minute: Sign up Git push - fatal: write error: Bad file descriptor up vote 0 down vote favorite I'm new to Git, so please forgive me if this is a stupid question. On my initial push to GitHub, using git push origin master I'm getting following error(s): Counting objects: 1499, done. Delta compression using up to 16 threads. Compressing objects: 100% (1455/1455), done. error: pack-objects died of signal 923 MiB | 9.10 MiB/s fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly fatal: write error: Bad file descriptor Am I missing something? git push share|improve this question edited Mar 10 at 9:25 Aamir 1,121625 asked Mar 10 at 9:02 Carl Johnston 32 Maybe the remote hard drive disk is full? –jbaptperez Mar 10 at 9:07 Would that effect a push to GitHub? –Carl Johnston Mar 10 at 9:26 Your right, on github, you shouldn't have this kind of problem... Your kind of problem is analysed here, and a possibly solution is here –jbaptperez Mar 10 at 9:32 Thanks. Unfortunately that doesn't seem to have solved the problem. But thanks for the resources! –Carl Johnston Mar 10 at 9:38 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote I was getting same error few days back what worked for me was that default file post size for Git has been exceeded.So navigate to repo and run this command to increase the buffer to 500MB after navigating to the repository git config http.postBuffer 524288000 share|improve this answer answered Mar 10 at 9:09 Aamir 1,121625 Thanks for the response. I tried it, and it still returns the same error. I'm not sure what's going wrong, to know how to fix it. –Carl Johnston Mar 10 at 9:23 add a comment| up vote 1 down vote When I got this same error, the following command fixed this issue git config --global pack.wind
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Git push - fatal: write error: Bad file descriptor up vote 0 down vote favorite I'm new to Git, http://stackoverflow.com/questions/35911805/git-push-fatal-write-error-bad-file-descriptor so please forgive me if this is a stupid question. On my initial push to GitHub, using git push origin master I'm getting following error(s): Counting objects: 1499, done. Delta compression using up to 16 threads. Compressing objects: 100% (1455/1455), done. error: pack-objects died of signal 923 MiB | 9.10 MiB/s fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly fatal: write error: Bad file descriptor Am http://stackoverflow.com/questions/35911805/git-push-fatal-write-error-bad-file-descriptor/35915009 I missing something? git push share|improve this question edited Mar 10 at 9:25 Aamir 1,121625 asked Mar 10 at 9:02 Carl Johnston 32 Maybe the remote hard drive disk is full? –jbaptperez Mar 10 at 9:07 Would that effect a push to GitHub? –Carl Johnston Mar 10 at 9:26 Your right, on github, you shouldn't have this kind of problem... Your kind of problem is analysed here, and a possibly solution is here –jbaptperez Mar 10 at 9:32 Thanks. Unfortunately that doesn't seem to have solved the problem. But thanks for the resources! –Carl Johnston Mar 10 at 9:38 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote I was getting same error few days back what worked for me was that default file post size for Git has been exceeded.So navigate to repo and run this command to increase the buffer to 500MB after navigating to the repository git config http.postBuffer 524288000 share|improve this answer answered Mar 10 at 9:09 Aamir 1,121625 Thanks for the response. I tried it, and it still returns the same error. I'm not sure what's going wrong, to know how to fix it. –Carl Johnston Mar 10 at 9:23 add a comment| up vote
PG P E B Consultant 3
as Inappropriate ♦ ♦ t5541: Bad file descriptor I haven't had a lot of time to track down it down until today, but I've been getting failures in t5541-http-push-.sh. Several tests fail with the error "fatal: write error: Bad file descriptor". I have bisected this to "73776dc: Merge branch 'js/maint-1.6.6-send-pack-stateless-rpc-deadlock-fix' into js/maint-send-pack-stateless-rpc-deadlock-fix" Full test output follows: $ ./t5541-http-push.sh -v Initialized empty Git repository in /Users/brian/dev/git/t/trash directory.t5541-http-push/.git/ expecting success: cd "$ROOT_PATH" && mkdir test_repo && cd test_repo && git init && : >path1 && git add path1 && test_tick && git commit -m initial && cd - && git clone --bare test_repo test_repo.git && cd test_repo.git && git config http.receivepack true && ORIG_HEAD=$(git rev-parse --verify HEAD) && cd - && mv test_repo.git "$HTTPD_DOCUMENT_ROOT_PATH" Initialized empty Git repository in /Users/brian/dev/git/t/trash directory.t5541-http-push/test_repo/.git/ [master (root-commit) 0c973ae] initial Author: A U Thor <[hidden email]> 0 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 path1 /Users/brian/dev/git/t/trash directory.t5541-http-push Cloning into bare repository test_repo.git... done. /Users/brian/dev/git/t/trash directory.t5541-http-push ok 1 - setup remote repository expecting success: # In the URL, add a trailing slash, and see if git appends yet another # slash. cd "$ROOT_PATH" && git clone $HTTPD_URL/smart/test_repo.git/ test_repo_clone && sed -e " s/^.* \"// s/\"// s/ [1-9][0-9]*\$// s/^GET /GET / " >act <"$HTTPD_ROOT_PATH"/access.log && # Clear the log, so that it does not affect the "used receive-pack # service" test which reads the log too. # # We do this before the actual comparison to ensure the log is cleared. echo > "$HTTPD_ROOT_PATH"/access.log && test_cmp exp act Cloning into test_repo_clone... remote: Counting objects: 3, done. remote: Total 3 (delta 0), reused 0 (delta 0) Unpacking objects: 100% (3/3), done. ok 2 - no empty path components expecting success: rm -rf test_repo_clone && git clone $H