Re: DB corruption of first day of subversion

On 2004-11-10 13:08+0530, Ritesh Nadhani wrote:
> On 2004-11-10 11:45+0530, Ritesh Nadhani wrote:
> >Hello,
> >
> >We plan to move all our repository from CVS to subversion.
> >
> >We are using WinXP with SP2. I was successfuly able to create create a
> >repository and even was able to import my test project to the repository.
> >Our server is running as a standalone svnserve daemon listening on 3690
> >port. It is on 512Kbps dsl line (bandwith is pretty costly out here).
> >
> >One of our developers was also able to download the test project (around 5
> >MB with documenation and all) to his home machine. He did some
> >modification
> >to the code and checked in. All this process were OK.
> >
> >Now, suddenly looks like the whole berkely DB is corrupt. Whenever we are
> >now trying to create a new project in the repository - we are getting an
> >error: Berkely DB error while allocating new node ID (getting 'next-key' )
> >for filesystem f:\svnrepos/db, DB_NOTFOUND: No matching key/data pair
> >found.
> >
> >If I try to checkout a project, we get error:
> >
> >Reference to non-existent node 'd.0.1' in filesystem 'F:/svnrepos/db'
> >
> >What should I do? Is SVN known to have bugs with Windows XP SP2.
> >
> >Regards,
> >Ritesh
> >
> >>>>>>>>
>
> F: is just a partition on my hard-disk. I have 4 partition on the box.
>
> c:\windows - XP Files
> d:DATA - General data files
> e:softwares - all softwares are installed out here instead of \program
> files\ . Makes it easy to manage.
> f:\repos - I am using it only for Subversion repository so that backup are
> easy to do.
>
> This drive is not network mapped. I mean you cannot access it from any
> machine in the networked. The only folder on this machine that can be
> accessed by other people is the SHareDocs which is present in C;\. Disk
> management shows it as:
>
> Type: Local disk
> Filesystem: NTFS.
>
> Am I missing something?

No, SVN should work on winXP OK. Couple of questions more,

1) What version of Subversion you are using?

2) Is the machine otherwise stable? Any flaky memory? Have you tried
   http://www.memtest86.com/ on it? Subversion could push quite a lot
   of stress to the I/O sub system and memory, so it is possible that it
   might trigger random memory errors on unstable HW.

BR, Jani

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