mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus 2011-03-24 16:25:44 +00:00 • committed by admin
parent 31bf31583b
commit e691727f24
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/forum/Behaviour_of_fsck.mdwn Normal file
View file

@ -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.