On 28-Jun-07, at 1:18 PM, Andreas Hasenack wrote:
> On Thu, Jun 28, 2007 at 04:55:20PM +0100, Melikian, Chris wrote:
>> On the other hand, I've become very disillusioned with the lack of
>> documentation and tools on how to recover from corrupted
>> revisions. The
>> problem we have is that we are trying to an "svnadmin dump" of our
>> repository in order to shrink it with svndumpfilter and we are
>> getting
>>
>> "Error: Invalid diff stream: insn 1245 cannot be decoded"
>>
>> errors. We are using svn 1.3.2 on Solaris with FSFS as the back
>> end and
>> svnserve as our repository access front end.
>
> At least the BDB backend has recovery. FSFS doesn't.
>
> I have used BDB with very large repositories (~50Gb) and it
> survived many
> hardware failures (after running recovery and with proper log files
> archived). Now I'm also using FSFS, and had to spend about a week
> manually recovering from corruptions (caused by hardware failure).
Prevention is better than cure... People really should start looking
more seriously at ZFS (which won't deliver bad data to applications
in the case of hardware failure).
Of course this only applies to people who are really serious about
protecting their data.
--Toby
>
> So, BDB has more buttons to push and dials to adjust, but at least it
> had the recovery option which worked very well. But now I wouldn't
> recommend it anymore because subversion upstream focus more on FSFS.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 28 18:57:34 2007