Can rm -rf / Really Wipe Your System? What POSIX Says and Real‑World Tests

Many stories warn that running rm -rf / will destroy a system, but according to POSIX.1-2008 the command is not executed; it prints an error when the operand resolves to the root directory.

“rm -rf / will not be executed.”

The specification states that if the pathname component is “/” or resolves to the root, rm must write a diagnostic message to standard error and do nothing else.

Only coreutils versions prior to 5.1.0 (released January 2004) lack this safeguard. Versions 5.1.0 and later, such as the 8.22 package on CentOS 7.2, refuse to run the command and suggest using --no-preserve-root to override.

Example on CentOS 7.2 (coreutils 8.22):

sudo rm -rf / rm: it is dangerous to operate recursively on '/' rm: use --no-preserve-root to override this failsafe

Even when the arguments are empty variables that expand to “/”, the same error appears:

sudo rm -rf $foo/$bar rm: it is dangerous to operate recursively on '/' rm: use --no-preserve-root to override this failsafe

Using the dangerous option --no-preserve-root disables the protection and attempts to delete the entire filesystem, resulting in numerous “operation not permitted” messages and eventually a non‑functional system.

Thus, on modern Linux distributions the “rm -rf /” myth is largely debunked; the command is blocked unless explicitly overridden.