summaryrefslogtreecommitdiff
path: root/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment')
-rw-r--r--doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment12
1 files changed, 0 insertions, 12 deletions
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
deleted file mode 100644
index fb3838511..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!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.
-"""]]