diff --git a/content/post/2016-12.md b/content/post/2016-12.md
index 9fba3de7b..fd078fed2 100644
--- a/content/post/2016-12.md
+++ b/content/post/2016-12.md
@@ -130,3 +130,32 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
- I enabled logging of `/rest/` and I think I'll leave it on for good
- Also, the disk is nearly full because of log file issues, so I'm running some compression on DSpace logs
- Normally these stay uncompressed for a month just in case we need to look at them, so now I've just compressed anything older than 2 weeks so we can get some disk space back
+
+## 2016-12-04
+
+- I got a weird report from the CGSpace checksum checker this morning
+- It says 732 bitstreams have potential issues, for example:
+
+```
+------------------------------------------------
+Bitstream Id = 6
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
+Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
+Result = Bitstream marked deleted in bitstream table
+-----------------------------------------------
+...
+------------------------------------------------
+Bitstream Id = 77581
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = 9959301aa4ca808d00957dff88214e38
+Checksum Calculated =
+Result = The bitstream could not be found
+-----------------------------------------------
+```
+
+- The first one seems ok, but I don't know what to make of the second one...
+- I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in `[dspace-dir]/assetstore/99/59/30/...`)
+- For what it's worth, there is no item on DSpace Test or S3 backups with that checksum either...
diff --git a/public/2016-12/index.html b/public/2016-12/index.html
index 5373f8e63..51fae7a96 100644
--- a/public/2016-12/index.html
+++ b/public/2016-12/index.html
@@ -30,7 +30,7 @@
-
+
@@ -245,6 +245,38 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
Normally these stay uncompressed for a month just in case we need to look at them, so now I’ve just compressed anything older than 2 weeks so we can get some disk space back
+2016-12-04
+
+
+- I got a weird report from the CGSpace checksum checker this morning
+- It says 732 bitstreams have potential issues, for example:
+
+
+------------------------------------------------
+Bitstream Id = 6
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
+Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
+Result = Bitstream marked deleted in bitstream table
+-----------------------------------------------
+...
+------------------------------------------------
+Bitstream Id = 77581
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = 9959301aa4ca808d00957dff88214e38
+Checksum Calculated =
+Result = The bitstream could not be found
+-----------------------------------------------
+
+
+
+- The first one seems ok, but I don’t know what to make of the second one…
+- I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in
[dspace-dir]/assetstore/99/59/30/...)
+- For what it’s worth, there is no item on DSpace Test or S3 backups with that checksum either…
+
+
diff --git a/public/index.xml b/public/index.xml
index 215fe7107..d250dbc16 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -148,6 +148,38 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
<li>Also, the disk is nearly full because of log file issues, so I’m running some compression on DSpace logs</li>
<li>Normally these stay uncompressed for a month just in case we need to look at them, so now I’ve just compressed anything older than 2 weeks so we can get some disk space back</li>
</ul>
+
+<h2 id="2016-12-04">2016-12-04</h2>
+
+<ul>
+<li>I got a weird report from the CGSpace checksum checker this morning</li>
+<li>It says 732 bitstreams have potential issues, for example:</li>
+</ul>
+
+<pre><code>------------------------------------------------
+Bitstream Id = 6
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
+Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
+Result = Bitstream marked deleted in bitstream table
+-----------------------------------------------
+...
+------------------------------------------------
+Bitstream Id = 77581
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = 9959301aa4ca808d00957dff88214e38
+Checksum Calculated =
+Result = The bitstream could not be found
+-----------------------------------------------
+</code></pre>
+
+<ul>
+<li>The first one seems ok, but I don’t know what to make of the second one…</li>
+<li>I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in <code>[dspace-dir]/assetstore/99/59/30/...</code>)</li>
+<li>For what it’s worth, there is no item on DSpace Test or S3 backups with that checksum either…</li>
+</ul>
diff --git a/public/post/index.xml b/public/post/index.xml
index 5f09a3747..34b152367 100644
--- a/public/post/index.xml
+++ b/public/post/index.xml
@@ -148,6 +148,38 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
<li>Also, the disk is nearly full because of log file issues, so I’m running some compression on DSpace logs</li>
<li>Normally these stay uncompressed for a month just in case we need to look at them, so now I’ve just compressed anything older than 2 weeks so we can get some disk space back</li>
</ul>
+
+<h2 id="2016-12-04">2016-12-04</h2>
+
+<ul>
+<li>I got a weird report from the CGSpace checksum checker this morning</li>
+<li>It says 732 bitstreams have potential issues, for example:</li>
+</ul>
+
+<pre><code>------------------------------------------------
+Bitstream Id = 6
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
+Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
+Result = Bitstream marked deleted in bitstream table
+-----------------------------------------------
+...
+------------------------------------------------
+Bitstream Id = 77581
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = 9959301aa4ca808d00957dff88214e38
+Checksum Calculated =
+Result = The bitstream could not be found
+-----------------------------------------------
+</code></pre>
+
+<ul>
+<li>The first one seems ok, but I don’t know what to make of the second one…</li>
+<li>I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in <code>[dspace-dir]/assetstore/99/59/30/...</code>)</li>
+<li>For what it’s worth, there is no item on DSpace Test or S3 backups with that checksum either…</li>
+</ul>
diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml
index e6046a835..19c59c8db 100644
--- a/public/tags/notes/index.xml
+++ b/public/tags/notes/index.xml
@@ -147,6 +147,38 @@ org.apache.solr.client.solrj.SolrServerException: Server refused connection at:
<li>Also, the disk is nearly full because of log file issues, so I’m running some compression on DSpace logs</li>
<li>Normally these stay uncompressed for a month just in case we need to look at them, so now I’ve just compressed anything older than 2 weeks so we can get some disk space back</li>
</ul>
+
+<h2 id="2016-12-04">2016-12-04</h2>
+
+<ul>
+<li>I got a weird report from the CGSpace checksum checker this morning</li>
+<li>It says 732 bitstreams have potential issues, for example:</li>
+</ul>
+
+<pre><code>------------------------------------------------
+Bitstream Id = 6
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = a1d9eef5e2d85f50f67ce04d0329e96a
+Checksum Calculated = a1d9eef5e2d85f50f67ce04d0329e96a
+Result = Bitstream marked deleted in bitstream table
+-----------------------------------------------
+...
+------------------------------------------------
+Bitstream Id = 77581
+Process Start Date = Dec 4, 2016
+Process End Date = Dec 4, 2016
+Checksum Expected = 9959301aa4ca808d00957dff88214e38
+Checksum Calculated =
+Result = The bitstream could not be found
+-----------------------------------------------
+</code></pre>
+
+<ul>
+<li>The first one seems ok, but I don’t know what to make of the second one…</li>
+<li>I had a look and there is indeed no file with the second checksum in the assetstore (ie, looking in <code>[dspace-dir]/assetstore/99/59/30/...</code>)</li>
+<li>For what it’s worth, there is no item on DSpace Test or S3 backups with that checksum either…</li>
+</ul>