Bernd.Hofner@gmx.net wrote:
> The bluescreen occured on my notebook, NOT on the repository server!
> The bluescreen and the repository problem are NOT related, because the
> bluescreen took place
> well after the repository crash and in a different configuration (new svn
> version, new repository location),
> that is still working after the bluescreen.
> And this has been the first bluescreen for ages! This seems strange,
don't
> you think?
> I didn't install new hardware or drivers.
>
Just because you didn't install anything new doesn't mean it isn't a bad
driver or failing hardware...maybe Subversion stresses it more than you
were or it's hardware just starting to fail. Applications cannot
directly cause bluescreens and TSVN and Subversion are just normal
applications (that do a ton of disk activity). Of course, a bug in
Windows or a driver could be hit by Subversion and cause a
bluescreen...but that is hardly Subversion's problem. Did you take note
of the module and error code on the bluescreen? Sometimes that is a
good hint.
> Regarding moving (well, recreating, since the old one is wrecked) the
> repository
> to another disk: As stated in my last mail, I did that (alas together with a
> svn version upgrade).
> So if everything keeps working, we can't be sure what the problem was...
> Sorry about that, but I'm getting a bit restless here,
> because I need to keep my motivation up to introduce a versioning system at
> all.
> (Hey, I've been a standalone, version-system-less developer for at least the
> last 10 years,
> so why bother?)
> If the introduction creates lots of additional work and unreliable results,
> I will
> loose my faith and good intentions... ;-)
>
> Bernd
No version control at all for ten years? That is just scary. :)
We've been using Subversion for several repositories on several machines
with many clients (mostly using svn:// protocol) without a single
repository problem for over 3 months now. All servers and clients on
Win2k, or XP, or 2003.
As you have suggested, it is hard to do any diagnosis or help very much
without a repro recipe...but keep us informed if you find any helpful
information.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 12 16:40:12 2003