Repo corrupted again, no idea why

[Luis Navarro]

Thanks again for everyone who responded with very useful information.
Special thanks to Adrian who started the new Wiki page on hard linked
clones....I think that will be very helpful for people who aren't familiar
with this issue.

I've got a few follow-up questions:

1) Is "hg clone" (without --pull option) the *only* Mercurial / THG
operation that creates hard links?

2) Regarding the "breaking hard link" method that Mercurial is supposed to
use in the normal case (no Windows shares, hard links in use), this method
is only used to break the hard links for files that are being updated,
right?  In other words, if my repo has 100 hard links and 3 existing files
are modified and committed, Mercurial's only going to "break the hard links"
for those 3 files, right?

3) Regarding the recent Mercurial fix to address the Windows API deficiency,
does this workaround only come into play for clone operations?  Or does it
come into play for commits, pushes, etc as well?

4) I was able to obtain hlscan.exe from the Windows Server 2003 Resource Kit
Tools download and determined that all of the repos (dev and staging) on
"Server A" do have hard links.  The production repo on "Server B" does not.
As a result, I believe the following will fix my situation going forward:

Step 1 - Upgrade all of our Mercurial and THG installs to the latest
versions
Step 2 - Recreate all repos from the production repo using "hg clone --pull"

Is this correct?

5) Regarding #4, if I want to employ hard links for efficiency reasons, I
could drop the "--pull" option and still be safe *if* everyone who uses
these repos (even over shares) uses the new fixed versions of Mercurial
and/or THG, right?  (More specifically, I'd have to create the first Server
A repo from production and then the rest of the Server A repos from that
first one I just created.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20101003/5c5e1476/attachment.html>