summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-01-14 19:06:38 +0000
committerGravatar admin <admin@branchable.com>2013-01-14 19:06:38 +0000
commitcaeedad95b491afb9286850817bc876f1b2d6a86 (patch)
tree93bcdb14569a0555d1ebb4bc50a5af79fd914145
parent7efe7b0238b51188acd0ca0340b005c90cbf45ee (diff)
Added a comment
-rw-r--r--doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment
new file mode 100644
index 000000000..f7d6221de
--- /dev/null
+++ b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="4.154.7.238"
+ subject="comment 3"
+ date="2013-01-14T19:06:37Z"
+ content="""
+I would doubt you'd have three broken drives, or read errors from 3 drives.
+
+You can use `sha256sum` to checksum the files in `bad` yourself, and compare the results with their names.
+If it matches, that would point to some kind of bug in fsck.
+"""]]