Re: svn commit: r11060 - trunk/www

[Max Bowsher <ma...@ukf.net>]

jaa@tigris.org wrote:
> Author: jaa
> Date: Mon Sep 20 21:22:10 2004
> New Revision: 11060
>
> Modified:
>   trunk/www/project_faq.html
> Log:
> Added a new entry, '#def-wedged-repository' which tries to explain what
> we mean when we say that a repository is wedged.
>
> * www/project_faq.html
>    (def-wedged-repository): ditto.
>
>
> Modified: trunk/www/project_faq.html
> Url:
> http://svn.collab.net/viewcvs/svn/trunk/www/project_faq.html?view=diff&rev=11060&p1=trunk/www/project_faq.html&r1=11059&p2=trunk/www/project_faq.html&r2=11060
> ==============================================================================
> --- trunk/www/project_faq.html (original) +++ trunk/www/project_faq.html 
> Mon
> Sep 20 21:22:10 2004 @@ -171,6 +171,8 @@
>     uses?</a></li>
> <li><a href="#bikeshed">What's a 'bikeshed'?</a></li>
> <li><a href="#baton">What's a 'baton'?</a></li>
> +<li><a href="#def-wedged-repository">What do you mean when you say that
> +    repository is 'wedged'?</a></li>
>
> <![CDATA[=========================================================]]>
>
> @@ -2114,6 +2116,34 @@
> developers call the structures "batons" because they're passed around
> quite a bit.</p>
>
> +<![CDATA[-----------------------------------------------------------]]>
> +
> +<h3><a name="def-wedged-repository">What do you mean when you say that
> +    repository is 'wedged'?</a></h3>
> +
> +wedged repository:
> +<blockquote>
> +A Subversion repository consists of two different internal parts, a
> +working compartment and a storage compartment.  A wedged repository is
> +a repository where the working compartment is unaccessible for some
> +reason, but the storage compartment is intact.  Therefore, a wedged
> +repository has not suffered any loss of data, but the working
> +compartment has to be corrected before you can access the
> +repository. See <a href="#stuck-bdb-repos">this</a> entry for details
> +how to do that.
> +</blockquote>
> +
> +corrupted repository:
> +
> +<blockquote>
> +A corrupted Subversion repository is a repository where the storage
> +compartment has been damaged, and therefore there is some degree of
> +real data loss in the repository.
> +</blockquote>
> +
> +<p>You might also like to check The Jargon File's definition for
> +<a href="http://catb.org/~esr/jargon/html/W/wedged.html">'wedged'</a>.
> +</p>
> </div>
> </body>
> </html>

The compartment analogy is somewhat forced - I'd say we should be expressing 
ourselves in terms of locks being left behind.

Also, nowhere does the above say we are talking about BDB repositories.

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn commit: r11060 - trunk/www

[David James <st...@gmail.com>]

I'm concerned that some users might be scared away from Subversion
based on the vague talk of 'wedged' and 'corrupted repositories' in
this FAQ entry.

Do you think this language is clearer? "If Subversion is shut down
uncleanly (e.g. the power fails), its database can be left in an
inconsistent (or 'wedged') state. In most cases, this situation can be
easily fixed by running the 'svnadmin recover' command, which rewinds
the repository back to a consistent state; see this question for
details."

Cheers,

David

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn commit: r11060 - trunk/www

[Jani Averbach <ja...@jaa.iki.fi>]

On 2004-09-21 09:38+0100, Max Bowsher wrote:
> 
> The compartment analogy is somewhat forced - I'd say we should be 
> expressing ourselves in terms of locks being left behind.
> 
> Also, nowhere does the above say we are talking about BDB repositories.
> 

Both of points, which you were addressing, were intentional:

With different repository backends we can have different situations
when the repository is wedged. With Berkeley DB it is locks or
permissions for log files. With SQL BD it migth be left over
connections (exceeded max connections) or something else, with FSFS it
might be exceeded quota limit for files and so on.

And I intentionally didn't like to say Berkeley DB, for above reasons.

I tried to make above entry as non technical as possible, for person
who doesn't know shared memory, or perhaps even what lock files are. But
her/his repository is wedged and she/he is scared.

BR, Jani

-- 
Jani Averbach


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org