How long can a check run? (Or: is my repostitory corrupted?)

Asked by Jeroen Hellingman

I am running a check on my repository, and after a few moments it remains in the state "checking commit contents" For over half an hour, running at 50% CPU usage, without reading or writing any data at all. Even the rotating slash is not changing. Is this normal? Running bzr 2.2 on windows with a repository of about 1.5 GB, and a largest pack file slightly over a gig.

C:\Users\Jeroen\Documents\eLibrary\Books>bzr check
Checking working tree at 'C:/Users/Jeroen/Documents/eLibrary/Books'.
Checking branch at 'file:///C:/Users/Jeroen/Documents/eLibrary/Books/'.
Checking repository at 'file:///C:/Users/Jeroen/Documents/eLibrary/Books/'.
\ checking commit contents:inventories 0/2

Question information

Language:
English Edit question
Status:
Answered
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Martin Pool (mbp) said :
#1

Hi,

That seems a bit unusual but not impossible that it's still checking, depending on the contents of the repository. If it's still not complete, please let us know. If you do decide to interrupt it, you should get a traceback that you can attach here.

Can you help with this problem?

Provide an answer of your own, or ask Jeroen Hellingman for more information if necessary.

To post a message you must log in.