git annex fsck is a no-op in bare repos

What is says on the tin:

See http://lists.madduck.net/pipermail/vcs-home/2011-June/000433.html

Thinking about this some more, it would be difficult to do anything when bad content is found, since it also cannot update the location log.

So this may be another thing blocked by branching, assuming that is fixed in a way that makes .git-annex available to bare repos. --Joey

Even if there is nothing it can do, knowing that the data is intact, or not, is valuable in and as of itself. -- RichiH

While storing the data is no longer an issue in bare repos, fsck would need a special mode that examines all the location logs, since it cannot run thru the checked out files. --Joey

comment 1

And, maybe, a way to start a fsck from remote? At least when the other side is a ssh or git annex shell, this would work.

Comment by Richard — Mon Jun 13 12:58:52 2011

git annex fsck --from remote

Currently fsck silently ignores --to/--from. It should at least complain if it is not supported.

Comment by npouillard — Sat Jun 25 12:20:44 2011

Comments on this page are closed.