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.
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
----- Original Message -----
From: "D.J. Heap" <dj@shadyvale.net>
To: "Bernd.Hofner@gmx.net" <bernd.hofner@gmx.net>
Cc: <dev@subversion.tigris.org>
Sent: Tuesday, August 12, 2003 6:11 AM
Subject: Re: Repository wrecked again (using _local_ disk!)
> The bluescreen is strongly indicative of a driver or hardware
> problem...applications are not generally able to cause them (aside from
> stressing or using a flawed driver or hardware device). This could also
> explain the repository problems if the hardware or driver is not
> functioning correctly...can you try moving it to a normal hard disk for
> a while to see how it goes?
>
> You might ask on the TSVN list if others have seen the failed rename
> problem, but I have seen that occasionally just from Explorer + WinZip
> shell extensions installed. I'm not sure if I've seen it with a vanilla
> Explorer, but it would not surprise me at all.
>
> DJ
>
>
> Bernd.Hofner@gmx.net wrote:
> > I don't think so. I got administrator privileges. The repository has
been
> > created under my account.
> > Apache could create some branches in the repository, before the error
> > occured.
> > Furthjermore, the reovery has been running for quie a while before it
gave
> > up with the error messages.
> > I guess privilege checks would be done quite early in the recovery
process.
> >
> >
> > FYI: I tried to replay todays actions but with:
> >
> > - updated Subversion 0.26.0 (from 0.25.0)
> > - updated TortoiseSVN 0.15.2 (from 0.14.0)
> > - D:\DevRep as repository (a local IDE disk) instead of P:\DevRep (a
> > local USB 2.0 disk).
> >
> > So far, without problems.
> >
> > Maybe someone should check with the Berkeley guys if they consider a USB
> > connected drive as a network drive,
> > regarding the memory mapped files?
> >
> >
> > Note that I noticed another strange thing (now in the new environment
> > desribed above):
> > - I imported a directory (FrameWrk) using TortoiseSVN.
> > - I tried to rename the directory (to FrameWrk.imported)
> > - Windows denied the rename, telling me that there is some other
process
> > using the directory
> > - I closed all applications and all explorer windows, leaving a
clean
> > desktop, but to no avail
> > - I restared the machine and got a hung explorer (how? I closed them
all
> > before), which I killed with "End now..."
> > and then a bluescreen <gulp> (Note that I'm not used any longer to
> > bluescreens.
> > - after the reboot the rename was successful
> > I guess that the TortoiseSVN plugin somehow kept its fingers on the
> > directory after the import....
> >
> >
> > Regards,
> >
> > Bernd
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 12 17:29:00 2003