1 files changed, 2 insertions, 50 deletions
diff --git a/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html b/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
index 932bd6d3..e97bd2d1 100644
--- a/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
+++ b/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
@@ -70,53 +70,5 @@ a.textlink:before {
 <p>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). </p>
 <p>E-Mail me your thoughts at comments@mx.buetow.org!</p>
 <a class="textlink" href="../">Go back to the main site</a><br />
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<title>Offsite backup with ZFS (Part 2)</title>
-<link rel="shortcut icon" type="image/gif" href="/favicon.ico" />
-<style type="text/css">
-body {
-  margin: auto;
-  padding-left: 10px;
-  padding-right: 10px;
-  max-width: 900px;
-  font-family: sans-serif;
-  font-size: 18px;
-  background-color: #222;
-  color: #ffffef;
-}
-
-a {
-  color: #0ca;
-  text-decoration: none;
-}
-
-a:hover {
-  color: #c0f;
-  text-decoration: none;
-}
-
-img {
-  max-width: 600px;
-  max-height: 400px;
-  display: block;
-  margin: auto;
-}
-
-pre {
-  display: block;
-  background-color: #111;
-  color: #fff;
-  padding: 5px;
-  overflow-x: auto;
-}
-
-a.textlink:before {
-  content: " ⇒ ";
-  padding-left: 2px;
-}
-</style>
-</head>
-<body>
+</body>
+</html>