A tale of user-friendliness with "hg merge" and "hg rollback".

[Benoit Boissinot]

On Mon, Oct 12, 2009 at 10:06 PM, Rob Landley <rob at landley.net> wrote:
> I've been maintaining a little project in mercurial for a few years now, but I
> always had people send me patches instead of doing pulls and dealing with
> branches.
>
> [snip]
>
> So now I just want to just get the repository back to a state where I
> understood it, so I do an "hg rollback".  Hoping this would not only kick out
> this weird abstract uncommitted merge object, but maybe even remove the one
> commit I'd pulled from Mark that was hiding all my recent work, which was
> showing up as "tip".
>
> Except that doing this seems to have destroyed the entire repository.  After
> the rollback, the entire repository was... gone.  "hg log -v" listed nothing.
> "hg branches" listed nothing.  Even giving it explicit revision numbers well
> back in the history ("hg log -r 800") produced _nothing_.
>

Every revlog from the repo disappeared, the repo is basically empty now.
Any other hint to help us understand what might have happened (FS, OS, etc.) ?

thanks,

Benoit