Tar: Not Found in Archive Error: Why Using *.gz with tar -xzf Fails (and How to Fix It)

Table of Contents#

Understanding the "Tar: Not Found in Archive" Error
Why Using *.gz with tar -xzf Fails: The Shell Globbing Culprit
Common Scenarios Where This Error Occurs
How to Fix the Error: Step-by-Step Solutions
Best Practices to Avoid the Error
Conclusion
References

1. Understanding the "Tar: Not Found in Archive" Error#

First, let’s clarify what the error message actually means. When you see:

tar: file.gz: Not found in archive  
tar: Exiting with failure status due to previous errors

tar is telling you it cannot find a specific file (e.g., file.gz) inside the archive you’re trying to extract. This is not the same as "archive not found" (which would say tar: Cannot open archive.tar.gz: No such file or directory). Instead, the archive itself exists, but tar is looking for a file within it that doesn’t exist.

The confusion arises when users assume *.gz is a way to tell tar to "extract all .gz archives." In reality, the error stems from how your shell (e.g., Bash) processes the * wildcard before tar even runs.

2. Why Using `*.gz` with `tar -xzf` Fails: The Shell Globbing Culprit#

To understand the error, we need to talk about shell globbing (also called filename expansion). When you type a command with a wildcard like *.gz, your shell (not tar) expands the wildcard into a list of filenames matching the pattern before executing the command.

For example, if your current directory has two files: data1.tar.gz and data2.tar.gz, typing ls *.gz would be expanded by the shell to ls data1.tar.gz data2.tar.gz before ls runs.

Now, let’s apply this to tar -xzf *.gz. The tar command syntax for extraction is:

tar -xzf <archive-name> [files-to-extract]

Here:

-x: Extract files.
-z: Use gzip compression.
-f: Specify the archive file (required; must be the last flag before the archive name).

When you run tar -xzf *.gz, the shell expands *.gz into a list of matching filenames. Let’s break down two scenarios:

Scenario 1: Multiple `.gz` Files Exist#

If you have data1.tar.gz and data2.tar.gz, the shell expands *.gz to data1.tar.gz data2.tar.gz. The command becomes:

tar -xzf data1.tar.gz data2.tar.gz

tar interprets this as: "Extract the file named data2.tar.gz from the archive data1.tar.gz." If data2.tar.gz isn’t inside data1.tar.gz (which it almost never is), tar throws the "Not found in archive" error.

Scenario 2: Only One `.gz` File Exists#

If there’s only one .gz file (e.g., backup.tar.gz), the shell expands *.gz to backup.tar.gz, making the command:

tar -xzf backup.tar.gz

This works—but only by accident. The command is valid here because there’s only one filename, so tar uses it as the archive name. However, this "success" can mislead users into thinking *.gz is a safe shortcut, leading to errors when multiple .gz files are present later.

Key Takeaway#

The *.gz wildcard is expanded by the shell, not tar. If multiple .gz files exist, tar misinterprets the extra filenames as "files to extract" from the first archive, causing the error.

3. Common Scenarios Where This Error Occurs#

Now that we understand the root cause, let’s explore specific situations where the "Not found in archive" error pops up:

Scenario 1: Multiple `.tar.gz` Archives in the Directory#

As discussed earlier, if you have report.tar.gz, logs.tar.gz, and photos.tar.gz, running tar -xzf *.gz expands to:

tar -xzf report.tar.gz logs.tar.gz photos.tar.gz

tar tries to extract logs.tar.gz and photos.tar.gz from report.tar.gz—which don’t exist inside it.

Scenario 2: Filenames with Spaces or Special Characters#

Suppose you have an archive named my backup.tar.gz (with a space). The shell expands *.gz to "my backup.tar.gz" (quoted, but tar may still misinterpret it if not handled). If there’s another file like notes.tar.gz, the expanded command becomes:

tar -xzf my backup.tar.gz notes.tar.gz

Here, tar sees my as the archive name (invalid), leading to "Cannot open my: No such file or directory"—a related error.

Scenario 3: Confusing `.gz` with `.tar.gz`#

A .gz file is a single compressed file, while a .tar.gz is a tar archive compressed with gzip. If you run tar -xzf file.gz (where file.gz is just a gzipped file, not a tar archive), tar will fail to parse it as a tar archive, often with "unexpected EOF" or "invalid tar magic" errors. However, if you combine this with *.gz, you may still trigger "Not found in archive."

4. How to Fix the Error: Step-by-Step Solutions#

Now that we know why the error occurs, let’s fix it. Below are solutions for common scenarios:

Solution 1: Extract a Single Archive (Explicit Filename)#

The simplest fix is to use the exact archive name instead of *.gz. For example:

tar -xzf data1.tar.gz

This tells tar explicitly: "Extract the archive data1.tar.gz." No shell globbing confusion—just direct, clear syntax.

Solution 2: Extract Multiple `.tar.gz` Archives (Use a Loop)#

To extract all .tar.gz archives in a directory, use a for loop to process each file individually. This avoids shell globbing issues:

for archive in *.tar.gz; do  
  tar -xzf "$archive"  
done

for archive in *.tar.gz: Iterate over all .tar.gz files.
"$archive": Quotes handle filenames with spaces (e.g., "my backup.tar.gz").

Solution 3: Handle Filenames with Spaces or Special Characters#

If your archive has spaces (e.g., my docs.tar.gz), always quote the filename:

tar -xzf "my docs.tar.gz"  # Quoting works  
# Or escape spaces with backslashes:  
tar -xzf my\ docs.tar.gz

Solution 4: Verify the Archive is a Valid `.tar.gz`#

If you’re unsure if a .gz file is a tar archive, check its type with file:

file data.gz  
# Output for .tar.gz: "data.gz: gzip compressed data, last modified: ..., from Unix, original size 12345"  
# Output for plain .gz: "data.gz: gzip compressed data, last modified: ..." (no "tar" mention)

To extract a plain .gz file (not a tar archive), use gunzip or gzip -d instead of tar:

gunzip data.gz  # Extracts to data (removes .gz)  
# Or keep the original .gz file:  
gzip -dk data.gz  # -k = keep original; extracts to data

Solution 5: Extract Specific Files from an Archive#

If you want to extract specific files inside an archive (e.g., all .txt files), use tar’s pattern matching—but quote the pattern to prevent shell globbing:

tar -xzf archive.tar.gz --wildcards "*.txt"

Here, --wildcards "*.txt" tells tar to extract all .txt files from archive.tar.gz. The quotes ensure the * is passed to tar (not expanded by the shell).

5. Best Practices to Avoid the Error#

Preventing the error is easier than fixing it. Follow these tips:

1. Always Use Explicit Filenames#

Avoid *.gz unless you’re using a loop. Explicit filenames (data.tar.gz) make commands readable and avoid ambiguity.

2. Verify Archives Before Extraction#

Check what’s inside an archive with tar -tzf to avoid surprises:

tar -tzf data.tar.gz  # List contents of data.tar.gz

3. Handle Special Characters Carefully#

Always quote filenames with spaces or special characters (e.g., tar -xzf "my archive.tar.gz").

4. Use Tab Completion#

Type the first few letters of the archive name and press Tab to auto-complete. This avoids typos and ensures you’re using the correct filename.

5. Distinguish Between `.gz` and `.tar.gz`#

Remember:

.tar.gz: Use tar -xzf.
.gz (single file): Use gunzip or gzip -d.

6. Conclusion#

The "Tar: Not Found in Archive" error when using *.gz with tar -xzf is a classic case of shell globbing misunderstanding. By remembering that your shell expands * before tar runs, you can avoid misinterpreting the command. Always use explicit filenames for single archives, or loops for multiple archives, and verify your archives to ensure they’re valid .tar.gz files.

With these steps, you’ll turn frustrating errors into smooth, efficient command-line workflows.