git-fsck | 易学教程

unknown object type 0 at offset - all repo mirrors corrupted preventing filter-branch subdirectory-filter

阅读更多关于 unknown object type 0 at offset - all repo mirrors corrupted preventing filter-branch subdirectory-filter

问题 1) Problem Description I have several pack files saying unknown object type 0 at offset , and unlike 99% of posts on the web this isn't a local problem but appears in both remote and cloned repos. 2) What I want to do How do I simply remove those invalid references so that I'm not blocked from doing other operations on the repo? Ultimately, I want to run a git filter-branch --subdirectory command to split my 9.2G repo into submodules, but it chokes on these invalid pack files (note: index

unknown object type 0 at offset - all repo mirrors corrupted preventing filter-branch subdirectory-filter

阅读更多关于 unknown object type 0 at offset - all repo mirrors corrupted preventing filter-branch subdirectory-filter

How can I recover HEAD^'S tree?

阅读更多关于 How can I recover HEAD^'S tree?

问题 tl;dr: is it possible to recover HEAD^ 's tree if it is deleted and not pushed beforehand and if everything else is intact? I accidentally deleted part of my .git . I'm not entirely sure what's missing. Upon discovering that git push didn't work, I ran a git fsck : Checking object directories: 100% (256/256), done. Checking objects: 100% (1265/1265), done. broken link from commit f3419f630546ba02baf43f4ca760b02c0f4a0e6d to tree 29616dfefd2bff59b7fb3177e99b4a1efc7132fa broken link from commit

Recover staged but not committed files after 'git rm -rf'

阅读更多关于 Recover staged but not committed files after 'git rm -rf'

问题 On my local machine I removed files from folder. git init git add --all then I wrote (don't ask me, why! :) ) git rm -rf I don't commit, yet. Now I have empty folders in my project. In .git folder has objects with 53 Mb of files. How can I recover my files? I've tried programs like Drill Disc and Stellar, but not found my files. And I can't rollback from GIT. How can I recover the lost files? 回答1: (update) Use git fsck instead, it is a builtin command for retrieving files you have once added

How can I recover HEAD^'S tree?

阅读更多关于 How can I recover HEAD^'S tree?

tl;dr: is it possible to recover HEAD^ 's tree if it is deleted and not pushed beforehand and if everything else is intact? I accidentally deleted part of my .git . I'm not entirely sure what's missing. Upon discovering that git push didn't work, I ran a git fsck : Checking object directories: 100% (256/256), done. Checking objects: 100% (1265/1265), done. broken link from commit f3419f630546ba02baf43f4ca760b02c0f4a0e6d to tree 29616dfefd2bff59b7fb3177e99b4a1efc7132fa broken link from commit ccfe9502e24d2b5195008005d83155197a2dca25 to tree 0580c3675560cbfd3f989878a9524e35f53f08e9 broken link

What does git fsck stand for?

阅读更多关于 What does git fsck stand for?

问题 What is the meaning in behind the fsck command name? The documentation of the command does not seem to mention what the name stands for. 回答1: It stands for File System ChecK. The name is taken from the Unix fsck command, which is used to validate a file system. 回答2: It was first called: fsck-cached (git 0.99), to check the repository for errors then fsck-objects (git 0.99.8), in order to report what exactly is wrong with the object, instead of an ambiguous 'bad sha1 file'. and finally git

What does git fsck stand for?

阅读更多关于 What does git fsck stand for?

What is the meaning in behind the fsck command name? The documentation of the command does not seem to mention what the name stands for. Barmar It stands for File System ChecK. The name is taken from the Unix fsck command, which is used to validate a file system. It was first called: fsck-cached (git 0.99), to check the repository for errors then fsck-objects (git 0.99.8), in order to report what exactly is wrong with the object, instead of an ambiguous 'bad sha1 file'. and finally git fsck (git 1.5.0, January 2007) It reflects that Git was initially built as a file system, with a graph of

git fatal - the remote hung up unexpectedly but not RPC or permission or broken pipe related message

阅读更多关于 git fatal - the remote hung up unexpectedly but not RPC or permission or broken pipe related message

问题 I have seen many post here on SO about git fatal: the remote end hung up unexpectedly issue but none of them seem to be related to mine. All posts about this error on here are related to RPC, permission, broken pipe etc but the fatal error I get does not mention any of these. It looks just like below I went to github page and I noticed big red warning at the top telling me to change my password, so I thought that could be the problem. I changed password and then tried again to push my local

Recover staged but not committed files after 'git rm -rf'

阅读更多关于 Recover staged but not committed files after 'git rm -rf'

On my local machine I removed files from folder. git init git add --all then I wrote (don't ask me, why! :) ) git rm -rf I don't commit, yet. Now I have empty folders in my project. In .git folder has objects with 53 Mb of files. How can I recover my files? I've tried programs like Drill Disc and Stellar, but not found my files. And I can't rollback from GIT. How can I recover the lost files? (update) Use git fsck instead, it is a builtin command for retrieving files you have once added to git repository. git fsck --lost-found --unreachable after the command processing, retrieved files will be

Git: what is a dangling commit/blob and where do they come from?

阅读更多关于 Git: what is a dangling commit/blob and where do they come from?

I'm looking for the basic info on dangling commits & blobs. My repo seems fine. But I ran git fsck for the first time to see what it did and I have a long list of 'dangling blobs' and a single 'dangling commit'. What are these things? Where did they come from? Do they indicate anything unusual (good or bad) about the state of my repo? During the course of working with your git repository, you may end up backing out of operations, and making other moves that cause intermediary blobs, and even some things that git does for you to help avoid loss of information. Eventually (conditionally,