Launchpad itself

bzr: ERROR: No such file: '/srv/bazaar.launchpad.net/mirrors/00/00/23/81/.bzr/repository/indices/2b....rix'

Asked by Keith Hughitt

Hello,

For some reason, the development trunk on Launchpad for our team has become corrupted. Attempting to push or pull to the branch results in an error message:

"bzr: ERROR: No such file: '/srv/bazaar.launchpad.net/mirrors/00/00/23/81/.bzr/repository/indices/2b08137c9cd4e7edb0b56944e678d55c.rix'"

So far we have tested access from two different machine with the same result. Furthermore, attempting to view changes associated with the branch now result in a server error.

The problematic branch is:

https://code.edge.launchpad.net/~hv-dev/helioviewer.org/trunk

Finally, I also tried deleting the branch on Launcpad in order to re-upload it (https://answers.edge.launchpad.net/launchpad-code/+question/103812), however, Launchpad will not allow this, complaining:

"This branch cannot be deleted as it has 5 branches sharing revisions."

Unfortunately it does not specify which five branches are dependent on it, and even if it had, I'm not certain that they would all be owned by active users who could delete their own branches.

Do you have any suggestions? Any advice would be appreciated.

Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Keith Hughitt
Solved:
Last query:
Last reply:
Revision history for this message
Max Bowsher (maxb) said : 		#1

The five branches are (identified by just looking at the branch web page for every branch in the project):
https://code.edge.launchpad.net/~keith-hughitt/helioviewer.org/hv-yui-grids
https://code.edge.launchpad.net/~jwh376/helioviewer.org/jonathan-jstree
https://code.edge.launchpad.net/~jabeck/helioviewer.org/jaclyn-old
https://code.edge.launchpad.net/~jabeck/helioviewer.org/jaclyn
https://code.edge.launchpad.net/~keith-hughitt/helioviewer.org/2.0

However it's probably better to try to fix this branch than delete all those.

Revision history for this message
Max Bowsher (maxb) said : 		#2

In some mysterious and unknown way, one of the packs and its indices has been moved to obsolete_packs but is still listed in pack-names. The branch can be mended by moving them back.

Something like this ought to do the trick.

mkdir /tmp/mountpoint
sshfs bazaar.launchpad.net:~hv-dev/helioviewer.org/trunk /tmp/mountpoint
cd /tmp/mountpoint
mv .bzr/repository/obsolete_packs/2b08137c9cd4e7edb0b56944e678d55c.pack .bzr/repository/packs/
mv .bzr/repository/obsolete_packs/2b08137c9cd4e7edb0b56944e678d55c.*ix .bzr/repository/indices/
cd
fusermount -u /tmp/mountpoint

Revision history for this message
Keith Hughitt (keith-hughitt) said : 		#3

Hi Max,

Thanks for taking the time to respond. I tried your above suggestion, but when I attempt to mount the branch using sshfs, I get an error "read: Connection reset by peer." I tried a couple suggestions on the web (removing known_host entry and making sure fuse is installed) but still no luck.

I've never used sshfs before. Any suggestions? I tried using SSH to connect to Launchpad normally (not sure if that is actually possible but it seemed likely since you could mount a folder using a tool called "sshfs" but that did not work with the above URL).

Revision history for this message
Keith Hughitt (keith-hughitt) said : 		#4

Update:

Including my username in the bzrssh command enabled that to work. I followed the above steps, however, the problem still persists, e.g.:

bzr branch lp:helioviewer.org

"bzr: ERROR: No such file: '/srv/bazaar.launchpad.net/mirrors/00/00/23/81/.bzr/repository/indices/2b08137c9cd4e7edb0b56944e678d55c.rix'"

The offending file (2b08137c9cd4e7edb0b56944e678d55c.rix) exists in the obsolete packs directory. Should I move that to the location it is expecting to find it in? How about the other .*ix files?

Thanks again for your help.
Keith

Revision history for this message
Max Bowsher (maxb) said : 		#5

Hi Keith,

Please look again at the commands I suggested - they already include commands to move that file, and others, out of obsolete_packs to where they are expected.

Revision history for this message
Keith Hughitt (keith-hughitt) said : 		#6

Oops. I somehow missed the second mv command. That worked great. Thanks for your help, Max!

Revision history for this message
Brad Crittenden (bac) said : 		#7

This problem just happened to me with a bzr repository not hosted at Launchpad. I was able to move the pack and indices files and recovered.