File: Locating_errors_on_fsck.mdwn

package info (click to toggle)
git-annex 10.20250416-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 73,572 kB
  • sloc: haskell: 90,656; javascript: 9,103; sh: 1,469; makefile: 211; perl: 137; ansic: 44
file content (7 lines) | stat: -rw-r--r-- 479 bytes parent folder | download | duplicates (6) 
1
2
3
4
5
6
7
 
When I run `git-annex fsck` I see a lot of output passing by the screen. In the end, after many hours, I see an error count.

Now, how do I see what files had problems and what is wrong with them? I can't see any option mentioning a log file or similar mechanism in the man page. Would I need to re-run the command and discard STDOUT? At this point I'm not even sure that would work.

What is the proper way to run `fsck` so that I can examine the problems it finds?

Thank you.