Packfiles and compression in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Understanding git packfile creation

What is the output of the command git gc --aggressive --prune=now in a repository with many loose objects?

A It deletes all objects and resets the repository to an empty state.

B It compresses loose objects into packfiles and removes unreachable objects immediately.

C It creates packfiles but does not remove any loose objects.

D It only removes unreachable objects but does not create packfiles.

💡 Hint

Think about what aggressive garbage collection does in Git.

The git gc --aggressive --prune=now command compresses loose objects into packfiles and immediately removes unreachable objects, cleaning up the repository efficiently.

🧠 Conceptual

intermediate

Purpose of delta compression in Git packfiles

Why does Git use delta compression inside packfiles?

A To encrypt objects for security during transfer.

B To create backups of objects in case of corruption.

C To speed up network transfer by sending full copies of objects.

D To store only the differences between similar objects, reducing disk space usage.

💡 Hint

Think about how storing differences can save space.

Delta compression stores only the changes between similar objects, which reduces the size of packfiles and saves disk space.

❓ Troubleshoot

advanced

Diagnosing corrupted packfile error

You run git fsck and get an error about a corrupted packfile. Which command helps you safely rebuild packfiles to fix this?

A git reset --hard HEAD

B git clean -f -d

C git repack -a -d --window=50 --depth=50

D git checkout -- .

💡 Hint

Look for a command that repacks objects.

git repack rebuilds packfiles and can fix corruption by repacking all objects with specified options.

✅ Best Practice

advanced

Optimizing packfile compression for large repositories

Which approach is best to optimize packfile compression for a large repository with many similar files?

A Use <code>git gc --aggressive</code> periodically to maximize compression.

B Avoid using packfiles and keep all objects loose for faster access.

C Disable delta compression to speed up packfile creation.

D Manually delete packfiles to reduce disk usage.

💡 Hint

Aggressive garbage collection improves compression but takes more time.

Running git gc --aggressive compresses objects more thoroughly, which is ideal for large repositories with many similar files.

🔀 Workflow

expert

Sequence to safely reduce repository size using packfiles

What is the correct sequence of commands to safely reduce a Git repository size by compressing objects and removing unreachable data?

A 3,1,2,4

B 1,2,3,4

C 2,1,3,4

D 3,2,1,4

💡 Hint

Think about garbage collection first, then repacking, pruning, and finally checking.

First run git gc to clean and compress, then git repack -a -d to repack all objects, followed by git prune to remove unreachable objects, and finally git fsck to verify integrity.

Practice

1. What is the main purpose of Git packfiles?

easy

A. To create backups of the repository

B. To manage user permissions in Git

C. To track changes in the working directory

D. To store many Git objects efficiently by compressing and grouping them

Solution

1. Step 1: Understand what packfiles do

   Packfiles combine many Git objects into one file and compress them to save space.

2. Step 2: Compare options

   Only To store many Git objects efficiently by compressing and grouping them describes this purpose correctly; others describe unrelated Git features.

3. Final Answer:

   To store many Git objects efficiently by compressing and grouping them -> Option D

4. Quick Check:

   Packfiles = efficient storage [OK]

Hint: Packfiles compress and group objects to save space [OK]

Common Mistakes:

• Confusing packfiles with backups
• Thinking packfiles track working directory changes
• Assuming packfiles manage permissions

2. Which Git command is used to create or optimize packfiles by compressing objects?

easy

A. git repack

B. git clone

C. git checkout

D. git branch

Solution

1. Step 1: Identify commands related to packfiles

   git repack creates or optimizes packfiles by compressing objects.

2. Step 2: Eliminate unrelated commands

   git clone copies repos, git checkout switches branches, git branch manages branches; none handle packfiles.

3. Final Answer:

   git repack -> Option A

4. Quick Check:

   Repack = compress objects [OK]

Hint: Use git repack to compress objects into packfiles [OK]

Common Mistakes:

• Choosing git clone for packfile compression
• Confusing git checkout with repack
• Thinking git branch manages packfiles

3. What happens when you run git gc in a repository?

medium

A. It compresses objects and creates packfiles to optimize storage

B. It resets the repository to the last commit

C. It deletes all branches except master

D. It lists all remote repositories

Solution

1. Step 1: Understand git gc function

   git gc (garbage collection) compresses objects and creates packfiles to optimize repository storage.

2. Step 2: Check other options

   Options A, B, and D describe unrelated Git actions.

3. Final Answer:

   It compresses objects and creates packfiles to optimize storage -> Option A

4. Quick Check:

   git gc = compress and optimize [OK]

Hint: git gc cleans and compresses repo data into packfiles [OK]

Common Mistakes:

• Thinking git gc deletes branches
• Confusing git gc with reset
• Assuming git gc lists remotes

4. You ran git repack -a -d but got an error. What is a likely cause?

medium

A. You used invalid flags; -a and -d are not valid together

B. The repository has no loose objects to pack

C. You need to run the command inside the .git directory

D. You must commit changes before repacking

Solution

1. Step 1: Understand git repack flags

   -a packs all objects, -d deletes redundant packs; these flags are valid together.

2. Step 2: Identify common error cause

   If no loose objects exist, repack may error or do nothing because nothing to pack.

3. Final Answer:

   The repository has no loose objects to pack -> Option B

4. Quick Check:

   No loose objects = repack error [OK]

Hint: No loose objects means repack has nothing to do [OK]

Common Mistakes:

• Thinking flags -a and -d are invalid together
• Running repack outside repo root
• Believing uncommitted changes block repack

5. You want to reduce repository size by combining many small packfiles into one. Which command and option should you use?

hard

A. git clone --depth=1

B. git repack -a -d --window=50

C. git gc --aggressive

D. git fetch --prune

Solution

1. Step 1: Understand the goal

   You want to combine many small packfiles into one to reduce size.

2. Step 2: Analyze commands

   git gc --aggressive repacks and compresses more thoroughly, combining packfiles effectively.

3. Step 3: Check other options

   git repack -a -d is good but less thorough; git clone --depth=1 creates shallow clones; git fetch --prune cleans remotes.

4. Final Answer:

   git gc --aggressive -> Option C

5. Quick Check:

   Aggressive gc = best packfile compression [OK]

Hint: Use git gc --aggressive for best packfile compression [OK]

Common Mistakes:

• Choosing git repack without --aggressive for max compression
• Confusing shallow clone with packfile compression
• Using git fetch --prune for packfile management