On 29-Jun-07, at 4:07 PM, Andreas Hasenack wrote:
> On Fri, Jun 29, 2007 at 02:52:04PM -0400, Jing Xue wrote:
>>
>> Quoting "Melikian, Chris" <Chris.Melikian@uk.fid-intl.com>:
>>
>>> Hi Ulrich,
>>>
>>> I completely agree that you need to use backups but I think that
>>> subversion should also have some tools to repair revisions so
>>> that you
>>> can at least get the repository back into a consistent state
>>> even if
>>> there is data loss.
>>>
>>> Surely, any production-ready version control system has such a tool?
>>
>> Sorry if I'm missing something very obvious here, but assuming a
>> backup
>> implementation that ensures timely and completely verified
>> backups, why
>> would one insist on repairing the repository? AFAIK, a hotcopy
>> backup is a
>> good-to-go repository itself.
>
> Following this rationale, you could as well as toss all your /sbin/
> fsck*
> files. :)
ZFS has no fsck. The reasons why are quite relevant to this thread.
When was the last time your fsck reported corruption, and did you
find the root cause?
--Toby
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 29 22:17:46 2007