From 9566c72b93190b13521f02d2fcaad290f8c2b047 Mon Sep 17 00:00:00 2001
From: 
 "https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
 <Justin@web>
Date: Mon, 14 Jan 2013 21:57:30 +0000
Subject: Added a comment

---
 .../comment_5_899c4afbc988d81984c5c3397285bb01._comment      | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment

diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment
new file mode 100644
index 000000000..fb3838511
--- /dev/null
+++ b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
+ nickname="Justin"
+ subject="comment 5"
+ date="2013-01-14T21:57:30Z"
+ content="""
+If you have both the corrupted file and the good file you can use the `cmp` command to show exactly how they differ:
+
+    cmp -l file1 file2
+
+If files are regularly marked as corrupted you might have bad ram.
+"""]]
-- 
cgit v1.2.3