By searchguy on Jul 25, 2009
You see, I was working on my home system this afternoon, writing code instead of enjoying the summer weather, when I hit the following:
stgreen@blue:~/Projects/silv/work$ hg verify \*\* unknown exception encountered, details follow \*\* report bug details to http://www.selenic.com/mercurial/bts \*\* or email@example.com \*\* Mercurial Distributed SCM (version 1.1.2) \*\* Extensions loaded: Traceback (most recent call last): File "/usr/bin/hg", line 20, in ? mercurial.dispatch.run() [...] File "/usr/lib/python2.4/vendor-packages/mercurial/revlog.py", line 379, in parseindex index, nodemap, cache = parsers.parse_index(data, inline) ValueError: corrupt index file
This made me, shall we say, unhappy. This made me realize that I hadn't done a push to the "main" hg repository since I started the new project that I had just recently gotten working, so I was looking at losing more than a thousand lines of code.
But there you were, ZFS and Time Slider, ready to pick me up and get me back in the game:
You are the wind beneath my wings:
stgreen@blue:~/Desktop/work$ hg verify checking changesets checking manifests crosschecking files in changesets and manifests checking files 3209 files, 266 changesets, 3862 total revisions
I only lost 15 minutes of work, and those 15 minutes don't even matter, because for those 15 minutes, I was screwing around in a virtualized Ubuntu getting GWT hosting mode working. I only lost two small changes.
I have no idea what caused this problem. ZFS isn't reporting any errors on the drive, but the hg and virtualbox forums suggest that the vboxsf filesystem might be corrupting files. So, note to self: push to the main hg repository before cloning to the virtualized Ubuntu!
And I'm 100% serious about that marriage thing.