Skip to main content

rm — Remove Files & Directories Linux Destructive

rm (remove) deletes files and directories from your filesystem. It’s fast and powerful—and that’s exactly why it’s dangerous: in most Linux setups, deleted files do not go to a recycle bin.

Use rm for cleanup (logs, cache, backups) and for removing unwanted files (broken uploads, old builds, malware artifacts). But always operate with a “verify-first” mindset.

No undo by default

Once you run rm, recovery is not guaranteed. On VPS/server workloads, assume it’s permanent unless you have backups or snapshots.

Core Syntax​

rm [OPTION]... FILE...
  • Deletes one or more files.
  • For directories, you must use recursion: rm -r DIR

Options That Matter (Use Carefully)​

OptionMeaningWhen to Use
----
-rRemove directories recursivelyDelete folders like wp-content/cache/
-fForce: ignore missing files, never promptAutomation or stubborn deletes (high risk)
-iPrompt before each removalManual safety for critical files
-IPrompt once if removing many filesSafer bulk operations
-vVerbose: print what’s removedLogging/auditing in scripts
--no-preserve-rootAllows deleting /Never use in normal work
--helpShow helpQuick reference
--versionShow versionCompatibility checks
The most dangerous combo

rm -rf is commonly used—and commonly misused. One wrong path can wipe a project, a site, or a server.

Safe Workflow​

A practical habit that prevents accidents:

  1. Preview what will be deleted (ls, find ... -print)
  2. Use protection flags when unsure (-i or -I)
  3. Delete the smallest scope possible (target a directory, not /var/www broadly)
  4. Verify results (ls, disk usage)
ls -lah *.log

Best Practices​

  • Always preview with ls before using wildcards (*, ?.log, etc.).
  • Use -i (manual) or -I (bulk) when deleting anything important.
  • Prefer deleting contents (dir/*) rather than deleting the folder itself if apps expect the folder to exist.
  • Avoid running destructive commands as root unless you absolutely must.
  • For automated cleanup, log deletions with -v and redirect output to a file.
Pro safety trick

Use pwd before a destructive command to confirm your current directory.

pwd

Troubleshooting​

SymptomLikely CauseFix
--
Is a directoryYou tried to remove a folder without recursionUse rm -r DIR
Permission deniedFile owned by root or restricted permissionsUse sudo rm ... or fix ownership
Deleted wrong filesWildcards matched more than expectedPreview with ls first; use -i/-I
Folder not emptyNeeds recursive deleteAdd -r
Quick safety checks (HTML)
# Confirm location
pwd

# Preview what wildcard matches
ls -lah wp-content/cache/*

# Check ownership/permissions
ls -ld wp-content/cache

Cheat Sheet​

rm file.txt                # Delete single file
rm file1 file2             # Delete multiple files
rm -r folder               # Delete directory recursively
rm -rf folder              # Force delete without prompt (danger)
rm -i wp-config.php        # Interactive delete (safer)
rm *.log                   # Delete all log files in current dir
rm -rf wp-content/cache/*  # Delete contents, keep folder

Mini Quiz​

  1. What does rm -r do that plain rm cannot?
  2. Which option forces deletion without prompting?
  3. Why is rm -rf / dangerous?
  4. How would you delete only the contents of wp-content/cache/ but keep the folder?
Answers (peek after you try)
  1. It removes directories recursively. 2) -f. 3) It can wipe the entire filesystem. 4) rm -rf wp-content/cache/*.

Worked Examples (with expected output)

Read before running

Don’t copy/paste destructive commands on production unless you are 100% sure of the path.

Remove a single file​

rm error_log

Expected output: (silent success)

Remove multiple files​

rm file1.txt file2.txt style.css

Expected output: (silent success)

Remove a directory without -r (failure)​

rm wp-content/uploads

Expected output:

rm: cannot remove 'wp-content/uploads': Is a directory

Remove a directory recursively​

rm -r wp-content/cache

Expected output: (silent success)

Force delete without prompt (high risk)​

rm -rf wp-content/cache

Expected output: (silent success)

Double-check path

Before running, validate:

ls -ld wp-content/cache

Interactive deletion​

rm -i wp-config.php

Expected output:

rm: remove regular file 'wp-config.php'?

Bulk confirmation with -I (prompt once)​

rm -I *

Expected output (example):

rm: remove 150 arguments?

Verbose output​

rm -v old-backup.zip

Expected output:

removed 'old-backup.zip'

Combine -rv​

rm -rv logs/

Expected output (example):

removed directory 'logs/error'
removed directory 'logs'

Delete all .log files in current directory​

rm *.log

Expected output: (silent success)

Preview first
ls *.log

Delete .tmp files in uploads via wildcard​

rm wp-content/uploads/*.tmp

Expected output: (silent success)

Delete hidden file​

rm .htaccess

Expected output: (silent success)

Delete multiple extensions​

rm *.bak *.old

Expected output: (silent success)

Delete files older than 7 days (using find)​

find /var/www/html -name "*.log" -mtime +7 -exec rm {} \;

Expected output: (silent success)

Why find is safer than wildcards

You can precisely target by name and age, rather than relying on what * matches.

Delete with sudo (root-owned file)​

sudo rm /var/log/apache2/error.log

Expected output: (silent success)

Delete a specific month folder (keep parent)​

rm -rf wp-content/uploads/2025/09

Expected output: (silent success)

Delete all contents but keep the folder​

rm -rf wp-content/cache/*

Expected output: (silent success)

Delete .zip files via pipe (xargs)​

ls *.zip | xargs rm

Expected output: (silent success)

Safer alternative

xargs can behave badly with weird filenames. Prefer:

rm -- *.zip

Dangerous example (awareness only)​

rm -rf /

Expected output (example safety guard):

rm: it is dangerous to operate recursively on '/'
Never do this

Bypassing this protection with --no-preserve-root can destroy the whole system.

Safe delete logging (track what you removed)​

rm -v *.log >> deletion.log

Expected output (example):

removed 'error.log'
removed 'debug.log'