summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar eigengrau <eigengrau@web>2015-05-24 15:07:34 +0000
committerGravatar admin <admin@branchable.com>2015-05-24 15:07:34 +0000
commitcc357f0ff3625e1e491c236afa0cefcd3b26c352 (patch)
treece5957c6b2b95d5cb8d86da1f7b7ae5c59b8c651
parente8bed20d4c14a32c5592cba1e1c35d2403965817 (diff)
Added a comment
-rw-r--r--doc/bugs/git_annex_fsck_on_btrfs_devices/comment_1_f33d4cb9689f89f07bb97460e4f30be8._comment7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_1_f33d4cb9689f89f07bb97460e4f30be8._comment b/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_1_f33d4cb9689f89f07bb97460e4f30be8._comment
new file mode 100644
index 000000000..d186370d3
--- /dev/null
+++ b/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_1_f33d4cb9689f89f07bb97460e4f30be8._comment
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="eigengrau"
+ subject="comment 1"
+ date="2015-05-24T15:07:34Z"
+ content="""
+I suppose since an I/O error can be intermittent, the file can’t be outright regarded as bad. Also I’m not sure whether the read system call returns a dedicated error code for checksum errors.
+"""]]