Kyle Kline wrote:
> The docs indicate that FSFS is suited well for backup schemes, with
> the caveat that if a backup takes place while a commit is in progress,
> the db/current file may not indicate the true current rev in the
> db/revs directory.
>
> My backup software does not allow me to specify orders of files to
> avoid this, and I would like to avoid doing a hotcopy due to the size
> of the repository.
>
> If I needed to restore and my db/current file is out of date, Is it as
> simple as editing the file? I notice there are three values in the
> file, <current-rev> <unknown -- hash?> <unknown> ......
No, no _absolutely_ not!
I believe (but am not totally certain) that *decreasing* the current rev is
safe.
However, *increasing* the current rev is likely to cause severe badness, as
this will mean that the other two values (next available unique IDs for two
kinds of objects) would then be too old, and so the same 'unique' id could
be assigned to multiple objects! Undefined erroneous behaviour would likely
result.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 1 16:40:33 2005