From 932ab299ae4c03a045d1bbed7041c62b93e2d51f Mon Sep 17 00:00:00 2001 From: Joshua Boniface Date: Wed, 28 Sep 2016 18:58:14 -0400 Subject: [PATCH] Further tweaked wording --- content/2.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/2.md b/content/2.md index a956eee..4b8567e 100644 --- a/content/2.md +++ b/content/2.md @@ -12,10 +12,10 @@ RAID protects you against one and only one thing: a disk failure. It does **not* * Multiple disk failures beyond the RAID level chosen (e.g. both disks in a mirror, or 3 disks in a RAID-6). * Failure of the RAID controller itself (especially when using hardware RAID), the computer itself, or the environment (a flood, or fire, perhaps). * Data corruption on-disk from filesystem bugs, cosmic rays, or minor hardware or firmware failures. -* Malicious or accidental deletion or modification of files by yourself or another party, including viruses, bad application writes, or administrative mistakes (e.g. `mkfs` on an existing filesystem). +* Malicious or accidental deletion or modification of files by yourself or another party, including viruses, bad application writes, or administrative mistakes (e.g. `rm`ing the wrong file or `mkfs` on an existing filesystem). + +Even ZFS, designed specifically to prevent the third point, is still susceptable to the others. The adage is simple: "RAID replicates **everything**, even the stuff you don't want, like the deletion of that file you needed." For these reasons and more, RAID IS NOT A BACKUP! - -ZFS is an interesting case: while it does protect from corruption, it is still susceptable to the other failure modes and hence is still NOT A BACKUP!