summaryrefslogtreecommitdiff
path: root/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.md
diff options
context:
space:
mode:
Diffstat (limited to 'gemfeed/2016-04-16-offsite-backup-with-zfs-part2.md')
-rw-r--r--gemfeed/2016-04-16-offsite-backup-with-zfs-part2.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.md b/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.md
index 376ff829..f8152d7b 100644
--- a/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.md
+++ b/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.md
@@ -26,6 +26,6 @@ Whenever I update the offsite backup, I am doing it to the drive, which is kept
Furthermore, I added scrubbing ("zpool scrub...") to the script. It ensures that the file system is consistent and that there are no bad blocks on the disk and the file system. To increase the reliability, I also run a "zfs set copies=2 zroot". That setting is also synchronized to the offsite ZFS pool. ZFS stores every data block to disk twice now. Yes, it consumes twice as much disk space, making it better fault-tolerant against hardware errors (e.g. only individual disk sectors going bad).
-E-Mail your comments to `foo@paul.cyou` :-)
+E-Mail your comments to `paul@nospam.buetow.org` :-)
[Back to the main site](../)