diff options
author | 2011-03-24 16:25:44 +0000 | |
---|---|---|
committer | 2011-03-24 16:25:44 +0000 | |
commit | e691727f24e8d42f2bd402f08e89d5f29af96cb0 (patch) | |
tree | 67c0b8a3f1afaa5ed15e5037dd2bee67fcfb6bbd | |
parent | 31bf31583be78b589c4b78a0dc8705f54fd9946e (diff) |
-rw-r--r-- | doc/forum/Behaviour_of_fsck.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/Behaviour_of_fsck.mdwn b/doc/forum/Behaviour_of_fsck.mdwn new file mode 100644 index 000000000..29aa3ec64 --- /dev/null +++ b/doc/forum/Behaviour_of_fsck.mdwn @@ -0,0 +1,13 @@ +The current behaviour of 'fsck' is a bit verbose. I have an annex'd directory of tarballs for my own build system for "science" applications, there's about ~600 or blobs in my repo, I do occassionally like to run fsck across all my data to see what files don't meet the min num copies requirement that I have set. + +Would it be better for the default behaviour of fsck when it has not been given a path to only output errors and not bother to show that a file is ok for every single file in a repo. i.e. + + git annex fsck + +should show only 'errors' and maybe a simple indicator showing the status (show a spinner or dots?) and when + + git annex fsck PATH/FILE + +it should have the current behaviour? + +Right now the current fsck behaviour might get annoying for anyone who would want to run fsck with repos with lots of big files. |