Hi Felix,
Your SMART data looks good to me, except for the hard drive temperature.
Experiencing 53°C looks quite a lot to me. Yet, this should not be the
cause of your corrupted data.
Two data-corruption problems on the same server which looks independant
from each other, and occured at a quite l
Le mer. 13 janv. 2021 à 23:25, Bo Berglund a écrit :
>
> On Wed, 13 Jan 2021 12:58:59 +0100, Pierre Fourès
> wrote:
>
> Thanks for your comments Pierre! :)
>
You're welcome.
> So you mean I need to shut down the svn server first?
> I don't know how to do th
Hi Bo,
I understand your point and have done similar setup. I've first started
using a local svnadmin hotcopy to create a clean and safe copy of my
repository, and then, rsynced this folder to my remote server. As I can
handle a downtime on my svn server (in the middle of the night), I've
switched
Hi Joe,
How is it going ?
Have you moved the needle forward ?
Seeing you're running on a VPS, my guess would be an I/O saturation or
big latency, causing subversion taking a very long time to acknowledge
the file has securely been written down on the "hard drive". I've
experienced this quite a lo
Le ven. 23 août 2019 à 17:10, Mark Phippard a écrit :
>
> On Fri, Aug 23, 2019 at 11:06 AM Nathan Hartman
> wrote:
>>
>> On Fri, Aug 23, 2019 at 9:53 AM Mark Phippard wrote:
>>>
>>> Anyway ... the only danger of a repository format is if you upgrade to
>>> latest and then for some reason need
Hello,
Le jeu. 22 août 2019 à 16:47, Mark Phippard a écrit :
>
>
>> Cannot they become obsolete when a new version of SVN comes
>> out?
>
>
> No. It is a valid copy of the repository.
>
>> Are they portable across operating systems and
>> filesystems? (I fear not)
>
>
> Yes, they are absolutel
Hello,
Le jeu. 22 août 2019 à 15:52, Anton Shepelev a écrit :
>
> Andreas Stieger:
>
> >The dump format is not the best option for backups. The
> >restore time is much too slow as you need to recover from a
> >serialized format. In many hand-baked scripts the dump
> >method misses point-in-time r
Hello,
Le jeu. 22 août 2019 à 13:46, Andreas Stieger a écrit :
>
> The only extra consideration that would need to be made is when using
> write-through proxying (SVNMasterURI). Merely noting for completeness that
> you would need an extra Location block in your httpd configuration. But your
>
Le sam. 20 juil. 2019 à 20:54, Daniel Shahaf a écrit :
>
> Stefan Sperling wrote on Sat, 20 Jul 2019 09:51 +00:00:
> > But as a user I find it infuriating when software I use contains
> > artificial restrictions like this. We should assume our users know
> > what they are doing. Subversion is not
Le sam. 20 juil. 2019 à 16:55, Nico Kadel-Garcia a écrit :
>
> On Fri, Jul 19, 2019 at 7:41 AM Pierre Fourès wrote:
> >
> > Hi all,
> >
> > I have a script accessing an old svn server whom SSL certificate have
> > expired a long time ago. Up to
Le ven. 19 juil. 2019 à 20:44, Stefan Sperling a écrit :
>
> On Fri, Jul 19, 2019 at 08:38:57PM +0200, Stefan Sperling wrote:
> > On Fri, Jul 19, 2019 at 01:40:52PM +0200, Pierre Fourčs wrote:
> > > Hi all,
> > >
> > > I have a script accessing an old svn server whom SSL certificate have
> > > exp
Hi all,
I have a script accessing an old svn server whom SSL certificate have
expired a long time ago. Up to now, I was permanently accepting the
certificate on the first run of the script and then everything was
sailling smooth. I reinstalled a couple of months ago a new box where
this script was
12 matches
Mail list logo
