fsck --from
Fscking a remote is now supported. It's done by retrieving the contents of the specified files from the remote, and checking them, so can be an expensive operation. (Several optimisations are possible, to speed it up, of course.. This is the slow and stupid remote fsck to start with.) Still, if the remote is a special remote, or a git repository that you cannot run fsck in locally, it's nice to have the ability to fsck it. If you have any directory special remotes, now would be a good time to fsck them, in case you were hit by the data loss bug fixed in the previous release!
This commit is contained in:
parent
d36525e974
commit
90319afa41
8 changed files with 131 additions and 44 deletions
|
@ -212,6 +212,8 @@ subdirectories).
|
|||
|
||||
To avoid expensive checksum calculations, specify --fast
|
||||
|
||||
To check a remote to fsck, specify --from.
|
||||
|
||||
* unused
|
||||
|
||||
Checks the annex for data that does not correspond to any files present
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue