Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 257DD200BC1 for ; Wed, 2 Nov 2016 00:14:40 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 240F1160B02; Tue, 1 Nov 2016 23:14:40 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E5E5E160AF7 for ; Wed, 2 Nov 2016 00:14:38 +0100 (CET) Received: (qmail 19105 invoked by uid 500); 1 Nov 2016 23:14:37 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 19090 invoked by uid 99); 1 Nov 2016 23:14:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2016 23:14:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D9DD6C07CC for ; Tue, 1 Nov 2016 23:14:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.7 X-Spam-Level: X-Spam-Status: No, score=-1.7 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.999, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Bybo4HUh6-3n for ; Tue, 1 Nov 2016 23:14:34 +0000 (UTC) Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 7FF595FC87 for ; Tue, 1 Nov 2016 23:14:33 +0000 (UTC) Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 9D4EC20B01 for ; Wed, 2 Nov 2016 00:14:24 +0100 (CET) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3t7n9q2W4SzyvF; Wed, 2 Nov 2016 00:14:19 +0100 (CET) Subject: Re: Subversion Exception - cleanup To: Dan Atkinson , Johan Corveleyn , users@subversion.apache.org References: From: Stefan Message-ID: <3cce6191-bb22-65f3-a0f1-265c89335884@posteo.de> Date: Wed, 2 Nov 2016 00:14:09 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms090509080301060401010809" archived-at: Tue, 01 Nov 2016 23:14:40 -0000 This is a cryptographically signed message in MIME format. --------------ms090509080301060401010809 Content-Type: multipart/alternative; boundary="------------F49632ADFBB3EBC129AA8E27" This is a multi-part message in MIME format. --------------F49632ADFBB3EBC129AA8E27 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10/28/2016 16:12, Dan Atkinson wrote: > Hi Johan, > > The repository is on a local drive and I have several other > repositories on the same drive as well that were unaffected. > > I do some tasks (update/tag) on the repository via the command line. I > just checked and the version of SVN used on the command line is > 1.8.15.14429. > > In any case, when I restarted my machine this morning, my repo was no > longer corrupt. > > I don't know what caused it, or why it was fine again this morning, > but this is no longer an issue for me. > > Kind regards, Dan > > On 28 October 2016 at 14:43, Johan Corveleyn > wrote: > > [ Added Dan Atkinson to cc, because he asked us to :-). Dan, see > below. ] > > On Fri, Oct 28, 2016 at 12:51 AM, Stefan > wrote: > > On 10/27/2016 16:36, Dan Atkinson wrote: > >> Hi there, > >> > >> Firstly, I am not subscribed to this mailing list so would > appreciate > >> being explicitly CC'd in any responses. :-) > >> > >> When I attempted to update my repository, I received the > following update: > >> > >> Error: The working copy database at 'D:\Work\SVN\trunk' is corru= pt. > >> Error: Try a 'Cleanup'. If that doesn't work you need to do a fr= esh > >> checkout. > >> > >> When I attempted a cleanup, I received the following message: > >> > >> --------------------------- > >> Subversion Exception! > >> --------------------------- > >> Subversion encountered a serious problem. > >> Please take the time to report this on the Subversion mailing li= st > >> with as much information as possible about what > >> you were trying to do. > >> But please first search the mailing list archives for the error > message > >> to avoid reporting the same problem repeatedly. > >> You can find the mailing list archives at > >> http://subversion.apache.org/mailing-lists.html > > >> > >> Subversion reported the following > >> (you can copy the content of this dialog > >> to the clipboard using Ctrl-C): > >> > >> In file > >>=20 > 'D:\Development\SVN\Releases\TortoiseSVN-1.9.4\ext\subversion\subve= rsion\libsvn_client\cleanup.c' > >> line 227: assertion failed (svn_dirent_is_absolute(dir_abspath)= ) > >> --------------------------- > >> OK > >> --------------------------- > >> > >> > >> --------------------------- > >> TortoiseSVN > >> --------------------------- > >> Cleanup failed to process the following paths: > >> D:\Work\SVN\trunk > >> The working copy database at 'D:\Work\SVN\trunk' is corrupt. > >> Try a 'Cleanup'. If that doesn't work you need to do a fresh > checkout. > >> --------------------------- > >> OK > >> --------------------------- > >> > >> My version information is: > >> TortoiseSVN 1.9.4, Build 27285 - 64 Bit , 2016/04/24 13:59:58 > >> Subversion 1.9.4, -release > >> apr 1.5.2 > >> apr-util 1.5.4 > >> serf 1.3.8 > >> OpenSSL 1.0.2g 1 Mar 2016 > >> zlib 1.2.8 > >> SQLite 3.12.1 > >> > >> I am running Windows 10 v1511 (OS Build 10586.601). > >> > >> Our SVN server (VisualSVN Server) is running SVN 1.7.6 (r1370777= ) > >> > >> I did try to search the archives for similar problems but > received a > >> 403 from Google when I attempted it. > >> > >> If you require any further information, please let me know > directly. > >> > >> Kind regards, Dan Atkinson > > > > In case of a WC DB corruption I'd say your best bet is to do a fr= esh > > checkout and copy over locally modified files from the old > working copy > > to the new one. > > > > You can also try to debug/troubleshoot the database corruption > and try > > to repair the database (sqlite3 -> pragma integrity_check) but > unless > > you have a reason to try to save your working copy, there's > little point > > to do so, IMO. > > > > Although I doubt it's related to the corruption you ran into: You= r > > VisualSVN Server is quite outdated. I assume you are running > Visual SVN > > Server 2.5.6. I'd certainly suggest you to upgrade your server > to 2.5.26 > > at least (which will bring SVN up to 1.7.21). The upgrade should > be as > > simple as clicking through the installer. > > > > If possible, you'd even upgrade to a later one which will bring > SVN up > > to 1.8 or 1.9 (currently VisualSVN Server 3.5.6 is the > recommended version). > > It would of course be interesting to know how the working copy coul= d > have ended up being corrupt. Any idea how it got corrupted, Dan? > I just recalled that we had cases of WC db corruption in our office too on two machines, when they ran into a bluescreen. It was suggested that this is due to an SQLite bug which was fixed in SQLite 3.13: "Fix a locking race condition in Windows that can occur when two or more processes attempt to recover the same hot journal at the same time." [1] TSVN 1.9.4 is built against SQLite 3.12.1. The current stable nightly already raised SQLite to >=3D 3.13 I believe and hence the next TSVN version should contain the fix. Hence, if that merely same bug is also the cause for the problem the OP had, it should be fixed with the next version. Regards, Stefan [1] https://www.sqlite.org/changes.html --------------F49632ADFBB3EBC129AA8E27 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
On 10/28/2016 16:12, Dan Atkinson wrote:
Hi Johan,

The repository is on a local drive and I have several other repositories on the same drive as well that were unaffected.

I do some tasks (update/tag) on the repository via the command line. I just checked and the version of SVN used on the command line is 1.8.15.14429.

In any case,=C2=A0when I restarted my machine this morning, my repo was no longer corrupt.

I don't know what caused it, or why it was fine again this morning, but this is no longer an issue for me.

Kind regards, Dan

On 28 October 2016 at 14:43, Johan Corveleyn <jcorvel= @gmail.com> wrote:
[ Added Dan Atkinson to cc, because he asked us to :-). Dan, see below. ]

On Fri, Oct 28, 2016 at 12:51 AM, Stefan <luke1410@posteo.de> wrote:
> On 10/27/2016 16:36, Dan Atkinson wrote:
>> Hi there,
>>
>> Firstly, I am not subscribed to this mailing list so would appreciate
>> being explicitly CC'd in any responses. :-)
>>
>> When I attempted to update my repository, I received the following update:
>>
>> Error: The working copy database at 'D:\Work\SVN\trunk' is corrupt.
>> Error: Try a 'Cleanup'. If that doesn't work you need to do a fresh
>> checkout.
>>
>> When I attempted a cleanup, I received the following message:
>>
>> ---------------------------
>> Subversion Exception!
>> ---------------------------
>> Subversion encountered a serious problem.
>> Please take the time to report this on the Subversion mailing list
>> with as much information as possible about what<= br> >> you were trying to do.
>> But please first search the mailing list archives for the error message
>> to avoid reporting the same problem repeatedly.<= br> >> You can find the mailing list archives at
>> http://subversion.= apache.org/mailing-lists.html
>>
>> Subversion reported the following
>> (you can copy the content of this dialog
>> to the clipboard using Ctrl-C):
>>
>> In file
>>=C2=A0 'D:\Development\SVN\Releases\Tortoise= SVN-1.9.4\ext\subversion\subversion\libsvn_client\cleanup.c' >>=C2=A0 line 227: assertion failed (svn_dirent_is_absolute(dir_abspath))
>> ---------------------------
>> OK
>> ---------------------------
>>
>>
>> ---------------------------
>> TortoiseSVN
>> ---------------------------
>> Cleanup failed to process the following paths: >> D:\Work\SVN\trunk
>> The working copy database at 'D:\Work\SVN\trunk' is corrupt.
>> Try a 'Cleanup'. If that doesn't work you need to do a fresh checkout.
>> ---------------------------
>> OK
>> ---------------------------
>>
>> My version information is:
>> TortoiseSVN 1.9.4, Build 27285 - 64 Bit , 2016/04/24 13:59:58
>> Subversion 1.9.4, -release
>> apr 1.5.2
>> apr-util 1.5.4
>> serf 1.3.8
>> OpenSSL 1.0.2g=C2=A0 1 Mar 2016
>> zlib 1.2.8
>> SQLite 3.12.1
>>
>> I am running Windows 10 v1511 (OS Build 10586.601).
>>
>> Our SVN server (VisualSVN Server) is running SVN 1.7.6 (r1370777)
>>
>> I did try to search the archives for similar problems but received a
>> 403 from Google when I attempted it.
>>
>> If you require any further information, please let me know directly.
>>
>> Kind regards, Dan Atkinson
>
> In case of a WC DB corruption I'd say your best bet is to do a fresh
> checkout and copy over locally modified files from the old working copy
> to the new one.
>
> You can also try to debug/troubleshoot the database corruption and try
> to repair the database (sqlite3 -> pragma integrity_check) but unless
> you have a reason to try to save your working copy, there's little point
> to do so, IMO.
>
> Although I doubt it's related to the corruption you ran into: Your
> VisualSVN Server is quite outdated. I assume you are running Visual SVN
> Server 2.5.6. I'd certainly suggest you to upgrade your server to 2.5.26
> at least (which will bring SVN up to 1.7.21). The upgrade should be as
> simple as clicking through the installer.
>
> If possible, you'd even upgrade to a later one which will bring SVN up
> to 1.8 or 1.9 (currently VisualSVN Server 3.5.6 is the recommended version).

It would of course be interesting to know how the working copy could
have ended up being corrupt. Any idea how it got corrupted, Dan?
I just recalled that we had cases of WC db corruption in our office too on two machines, when they ran into a bluescreen. It was suggested that this is due to an SQLite bug which was fixed in SQLite 3.13:
"Fix a locking race condition in Windows that can occur when two or more processes attempt to recover the same hot journal<= /a> at the same time." [1]

TSVN 1.9.4 is built against SQLite 3.12.1. The current stable nightly already raised SQLite to >=3D 3.13 I believe and hence the= next TSVN version should contain the fix.
Hence, if that merely same bug is also the cause for the problem the OP had, it should be fixed with the next version.

Regards,
Stefan

[1] https://www.sqlite.org/changes.html

--------------F49632ADFBB3EBC129AA8E27-- --------------ms090509080301060401010809 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC BlowggZWMIIEPqADAgECAgMSWZ8wDQYJKoZIhvcNAQENBQAweTEQMA4GA1UEChMHUm9vdCBD QTEeMBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNp Z25pbmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwHhcN MTYwOTEzMDczMjMwWhcNMTcwMzEyMDczMjMwWjCByjEYMBYGA1UEAxMPQ0FjZXJ0IFdvVCBV c2VyMSEwHwYJKoZIhvcNAQkBFhJsdWtlMTQxMEBwb3N0ZW8uZGUxJDAiBgkqhkiG9w0BCQEW FXN0ZWZhbi5oZXR0QHBvc3Rlby5kZTEiMCAGCSqGSIb3DQEJARYTbHVrZTE0MTBAYXBhY2hl Lm9yZzEeMBwGCSqGSIb3DQEJARYPbHVrZTE0MTBAZ214LmRlMSEwHwYJKoZIhvcNAQkBFhJz dGVmYW4uaGV0dEBnbXguZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDe/SbZ aLYB+CQ8YF79gmmSaPHBd1KAhXqevB8AVjahmEgjq1ue3C0l+Wbe/k0sLYHLDlNOcDyDalZG +GNpeqqKiSxZinG7XANtpx5RYkQnh59625jR23zSF9C/mnINC1RS3IuH2IC975HUx05xbFNW TtnKKEHdlKRKIFsCsWp99PtcWuduEOp/7nqL+5yXmum46elzinwcHfvt5gxR2JTCAmKMKrYF oxWJSjMOGZzcZON8GSiEDk2z+kHVzFa/L+bh4AdyH3tOlebOONfKQ1Gf5Y21ftgUcXGdPxnT T3dbOPe5Os2LBhiyyv5rquPh+z/CtIPiEBNeY56G7RkRLB1BAgMBAAGjggGTMIIBjzAMBgNV HRMBAf8EAjAAMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUg Zm9yIEZSRUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAOBgNVHQ8BAf8E BAMCA6gwQAYDVR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMCBgorBgEEAYI3CgMEBgorBgEE AYI3CgMDBglghkgBhvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIGCCsGAQUFBzABhhZodHRwOi8v b2NzcC5jYWNlcnQub3JnMDEGA1UdHwQqMCgwJqAkoCKGIGh0dHA6Ly9jcmwuY2FjZXJ0Lm9y Zy9yZXZva2UuY3JsMG4GA1UdEQRnMGWBEmx1a2UxNDEwQHBvc3Rlby5kZYEVc3RlZmFuLmhl dHRAcG9zdGVvLmRlgRNsdWtlMTQxMEBhcGFjaGUub3JngQ9sdWtlMTQxMEBnbXguZGWBEnN0 ZWZhbi5oZXR0QGdteC5kZTANBgkqhkiG9w0BAQ0FAAOCAgEAit2IObDFStQZl50CFJbkm4Ws V8ZBnrEA1978P2MPQo0TN498EuQnUGWTbfDJLPodeu42cFw+QELH4DyUjZbYShskrYodJBVE aBWuCL4S1hIwM6lqSfFTbTEyywX8c4RHxQy4l4y72P8llBCwv1GO8/ZthrifRKq/sqzOgbHM nY+bB3UlveEpwcwK/3SMmDcq5GVUmpsPsiXq21G8SQMmZb9+3YM/VItrfAdNjAAaA8GWt648 0QQ0RuViUpzXkyCN1aLuqYXFzgNfL9aN2cKzM00U8zALT4RpuLBq25fU59Q9ssfHi4dKjjG7 xWUNhomo4ff977CUxW7RvYjIKLNBjF/fAf4gecGF7siHGlAHoAzTB39Z0NkRf7rl8Bz81nJY y0gu/E60xbphOugycM8o2woyIfm7AchvCtbkHwvd5zRSX+fBUxOwKhsFdcjdHIrGOX7TaggG iwwWY+aR13IIOSZR8/ojaUc5i1aUq/QJDluYUs2EYftacVFxw8a5ZtBUg1MrReprNikR5Sg5 RXDUcpLzxVjXXPP/d/aPN0tSuK3TtAZ96UN4x/oMdlYo01d4h+Ey9+XQAU4fxB58EsUT9oIY fiVG84dQCgq6PYRH1kUR4j4lo1QtXO/cch81JQkv6OgOehsV7ndlIwKmUcG8XMiwzCH/mfm0 4BpFL3Pu8JMxggOxMIIDrQIBATCBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVo dHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDElmfMA0GCWCGSAFlAwQC AQUAoIICATAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjEx MDEyMzE0MDlaMC8GCSqGSIb3DQEJBDEiBCB5gGv305MK8Rn5cVo7j+GzYt8jjlwD2awFrV43 B9+PADBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZI hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3 DQMCAgEoMIGRBgkrBgEEAYI3EAQxgYMwgYAweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwGA1UE CxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0 aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcCAxJZnzCBkwYLKoZI hvcNAQkQAgsxgYOggYAweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwGA1UECxMVaHR0cDovL3d3 dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0aG9yaXR5MSEwHwYJ KoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcCAxJZnzANBgkqhkiG9w0BAQEFAASCAQCo YhAu2MwJImhA/KQNmNdNeazmv3x/3KxLSvJXhd72+xM656w4nHpOiYX6do0N4j0UUL/MDRCm 8lYAsQuT43eNDKUy8/i3vAuLgT9YzZFANpIp7UxMLwg7t4Ryqec0FQ69TT4RngvdnLuHD07M 0mJnnZNZxHDrr9PFRiwExhIgaz9XWxX9ummSRBm2YKz4YBq77kZ0queQp8f82/GYW0giXvAk wnsjF2/GjIIsNvQkk6OfRKQGWYV57zn6CTrEWW1C0+RROaJfQNYakO4HZbeNvx5tTtelDqfK HL8Xdmxskx8N/OJBQypWpEJM7IqORC9uOmTbjpy9EdiDhn2F1E2YAAAAAAAA --------------ms090509080301060401010809--