From 54a8f9dd0fd90ca89fae4e24528ef9ebf2422ba9 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" Date: Sun, 14 Apr 2013 17:24:14 +0000 Subject: [PATCH] --- ..._in_direct_mode_does_not_checksum_files.mdwn | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files.mdwn diff --git a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files.mdwn b/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files.mdwn new file mode 100644 index 0000000000..a52a3c4fdb --- /dev/null +++ b/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files.mdwn @@ -0,0 +1,17 @@ +What steps will reproduce the problem? + +Put some large files into a direct mode repository (so fsck time is noticeable). git annex add them, commit, run git annex fsck. + +What is the expected output? What do you see instead? + +Expected: files are checksummed, which should take considerable amount of time for each file. For reference, in indirect mode, fsck takes a while for files of ~1GB size. +Actually: in direct mode, git annex fsck goes through all of the files in an instant and prints OK for each. I believe the file content is not verified. +Multiple runs of git annex fsck do the same thing. + +What version of git-annex are you using? On what operating system? + +git-annex version: 4.20130405, Linux + +Please provide any additional information below. + +