Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C32FAD17B for ; Fri, 9 Nov 2012 20:15:01 +0000 (UTC) Received: (qmail 12959 invoked by uid 500); 9 Nov 2012 20:15:01 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 12944 invoked by uid 500); 9 Nov 2012 20:15:00 -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 12936 invoked by uid 99); 9 Nov 2012 20:15:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 20:15:00 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of subversion@shenkin.org designates 128.227.74.71 as permitted sender) Received: from [128.227.74.71] (HELO smtp.ufl.edu) (128.227.74.71) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 20:14:54 +0000 Received: from [10.228.13.60] (ssrb-vpn2-13-60.vpn.ufl.edu [10.228.13.60]) (authenticated bits=0) by smtp.ufl.edu (8.14.0/8.14.0/3.0.0) with ESMTP id qA9KESEH023088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 9 Nov 2012 15:14:31 -0500 Message-ID: <509D6414.5010704@shenkin.org> Date: Fri, 09 Nov 2012 15:14:12 -0500 From: Alexander Shenkin User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: users@subversion.apache.org Subject: error: Revision file lacks trailing newline Content-Type: multipart/alternative; boundary="------------020501020406010403010803" X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8185,1.0.431,0.0.0000 definitions=2012-11-09_03:2012-11-09,2012-11-09,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1203120001 definitions=main-1211090195 X-Spam-Level: * X-UFL-Spam-Level: * X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------020501020406010403010803 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello Folks, I was getting an error while trying to checkout a directory, and some investigation with VisualSVN's server manager turned up an error in a couple of files ("Corrupt node-revision '5-2893.0.r2893/0' Missing id field in node-rev"). I then ran svnadmin verify, and got the following: ... * Verified revision 2433. * Verified revision 2434. * Verified revision 2435. svnadmin: E160004: Revision file (r2436) lacks trailing newline Looking online seems to indicate that this might have to do with commits > 4GB, though that was an old problem. Given that more than 1 file was problematic in the server manager, I figure there might be more than one corrupted revision. The damaged files aren't critical and haven't changed since being committed for the first time. I have working copies of them. Any thoughts about how I might go about repairing the repo? Thanks, Allie VisualSVN Server 2.5.2 svn 1.7.7 Win 7 Pro x64 SP1 TortoiseSVN 1.7.10 --------------020501020406010403010803 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello Folks,

I was getting an error while trying to checkout a directory, and some investigation with VisualSVN's server manager turned up an error in a couple of files ("Corrupt node-revision '5-2893.0.r2893/0' Missing id field in node-rev").

I then ran svnadmin verify, and got the following:
...
* Verified revision 2433.
* Verified revision 2434.
* Verified revision 2435.
svnadmin: E160004: Revision file (r2436) lacks trailing newline
Looking online seems to indicate that this might have to do with commits > 4GB, though that was an old problem.  Given that more than 1 file was problematic in the server manager, I figure there might be more than one corrupted revision.  The damaged files aren't critical and haven't changed since being committed for the first time.  I have working copies of them.

Any thoughts about how I might go about repairing the repo?

Thanks,
Allie

VisualSVN Server 2.5.2
svn 1.7.7
Win 7 Pro x64 SP1
TortoiseSVN 1.7.10
--------------020501020406010403010803--