more hints on technical issues due to shared-disk access of central Mercurial repository;
authorwenzelm
Mon Dec 17 14:51:34 2012 +0100 (2012-12-17)
changeset 50576325bf9073c59
parent 50575 ae1da46022d1
child 50578 9efc99c990d5
more hints on technical issues due to shared-disk access of central Mercurial repository;
Admin/Mercurial/Central/README
     1.1 --- a/Admin/Mercurial/Central/README	Mon Dec 17 14:07:34 2012 +0100
     1.2 +++ b/Admin/Mercurial/Central/README	Mon Dec 17 14:51:34 2012 +0100
     1.3 @@ -13,7 +13,9 @@
     1.4      fncache
     1.5  
     1.6  * See http://mercurial.selenic.com/wiki/MultipleCommitters for old-fashioned
     1.7 -  CVS-like multiple committers configuration, "The filesystem method":
     1.8 +  CVS-like multiple committers configuration, "The filesystem method".
     1.9 +
    1.10 +  A fresh multi-user clone is initialized like this:
    1.11  
    1.12      hg --config format.dotencode=0 init isabelle-clone
    1.13      cd isabelle-clone
    1.14 @@ -25,3 +27,26 @@
    1.15    Now isabelle-clone is ready for push of repository data (without making
    1.16    a working directory).
    1.17  
    1.18 +* Addressing technical issues: according to
    1.19 +  http://mercurial.selenic.com/wiki/PublishingRepositories our shared disk
    1.20 +  configuration (after regular ssh login) is characterized as follows:
    1.21 +
    1.22 +    Advantages: can use existing setup
    1.23 +
    1.24 +    Disadvantages: generally restricted to intranets, not generally
    1.25 +    recommended due to general issues with network filesystem reliability
    1.26 +
    1.27 +  Due to NFS instabilities of unknown origin at TUM, drop-outs have
    1.28 +  happened before. The following measures of last resort can be applied:
    1.29 +
    1.30 +    (a) "hg verify" to find offending changesets
    1.31 +        "hg strip REV" to remove parts of the public history by vivisection
    1.32 +
    1.33 +    (b) fresh clone from known-good source as explained above
    1.34 +
    1.35 +  Note that any such non-monotonic changes on the central push area work
    1.36 +  under the assumption of sequential single-user mode!!
    1.37 +
    1.38 +  See also http://mercurial.selenic.com/wiki/RepositoryCorruption for
    1.39 +  further background information.
    1.40 +