Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion error: Revision file lacks trailing newline

Received: by 10.66.87.234 with SMTP id bb10mr5600334pab.36.1352551474281;
        Sat, 10 Nov 2012 04:44:34 -0800 (PST)
X-BeenThere: subversion_users@googlegroups.com
Received: by 10.68.234.37 with SMTP id ub5ls19553902pbc.6.gmail; Sat, 10 Nov
 2012 04:44:34 -0800 (PST)
Received: by 10.66.81.200 with SMTP id c8mr5711743pay.1.1352551474234;
        Sat, 10 Nov 2012 04:44:34 -0800 (PST)
Received: by 10.66.81.200 with SMTP id c8mr5711742pay.1.1352551474221;
        Sat, 10 Nov 2012 04:44:34 -0800 (PST)
Return-Path: <users-return-16650-subversion_users+garchive-53313=googlegroups....@subversion.apache.org>
Received: from mail.apache.org (hermes.apache.org. [140.211.11.3])
        by gmr-mx.google.com with SMTP id uz6si297061pbc.0.2012.11.10.04.44.34;
        Sat, 10 Nov 2012 04:44:34 -0800 (PST)
Received-SPF: pass (google.com: domain of users-return-16650-subversion_users+garchive-53313=googlegroups....@subversion.apache.org designates 140.211.11.3 as permitted sender) client-ip=140.211.11.3;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of users-return-16650-subversion_users+garchive-53313=googlegroups....@subversion.apache.org designates 140.211.11.3 as permitted sender) smtp.mail=users-return-16650-subversion_users+garchive-53313=googlegroups....@subversion.apache.org
Received: (qmail 18755 invoked by uid 500); 10 Nov 2012 12:44:27 -0000
Mailing-List: contact users-h...@subversion.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-h...@subversion.apache.org>
List-Unsubscribe: <mailto:users-unsubscr...@subversion.apache.org>
List-Post: <mailto:us...@subversion.apache.org>
List-Id: <users.subversion.apache.org>
Delivered-To: mailing list us...@subversion.apache.org
Received: (qmail 18709 invoked by uid 99); 10 Nov 2012 12:44:25 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Nov 2012 12:44:25 +0000
X-ASF-Spam-Status: No, hits=-0.1 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS,WEIRD_PORT
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of subvers...@shenkin.org designates 128.227.74.165 as permitted sender)
Received: from [128.227.74.165] (HELO smtp.ufl.edu) (128.227.74.165)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Nov 2012 12:44:17 +0000
Received: from [192.168.2.120] ([190.34.5.82])
	(authenticated bits=0)
	by smtp.ufl.edu (8.14.0/8.14.0/3.0.0) with ESMTP id qAAChppN028981
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <us...@subversion.apache.org>; Sat, 10 Nov 2012 07:43:55 -0500
Message-ID: <509E4C02.5040...@shenkin.org>
Date: Sat, 10 Nov 2012 07:43:46 -0500
From: Alexander Shenkin <subvers...@shenkin.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: us...@subversion.apache.org
Subject: Re: error: Revision file lacks trailing newline
References: <509D6414.5010...@shenkin.org>
In-Reply-To: <509D6414.5010...@shenkin.org>
Content-Type: multipart/alternative;
 boundary="------------010400030304080601020200"
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8185,1.0.431,0.0.0000
 definitions=2012-11-10_05:2012-11-09,2012-11-10,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-1211100073
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.
--------------010400030304080601020200
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Problem solved.  Just wanted to post back so folks having the same
problem might benefit from my wasted day of troubleshooting.

Turned out that a few files in my FSFS repo had gotten corrupted.  I had
backups (thankfully), so I just replaced those couple files giving me
problems in 'svnadmin verify' with the backups, and that was that. 
There was one other file giving me problems (turned up as: "svn:
E175002: REPORT of '/svn/reponame/!svn/me': Could not read chunk size:
Secure connection truncated (https://mycomp:53239)" ).  I looked in the
windows event logs for the VisualSVN Server events, and turned out there
were permission problems.  I changed the permissions on the
corresponding file in the repo/db/revs file to match all the other files
in there (it must have gotten corrupted too), and now i'm running great.

Hope someone can benefit from my experience.

allie

On 11/9/2012 3:14 PM, Alexander Shenkin wrote:
> 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


--------------010400030304080601020200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Problem solved.&nbsp; Just wanted to post back so folks having the same
    problem might benefit from my wasted day of troubleshooting.<br>
    <br>
    Turned out that a few files in my FSFS repo had gotten corrupted.&nbsp; I
    had backups (thankfully), so I just replaced those couple files
    giving me problems in 'svnadmin verify' with the backups, and that
    was that.&nbsp; There was one other file giving me problems (turned up
    as: "<tt>svn: E175002: REPORT of '/svn/reponame/!svn/me': Could not
      read chunk size: Secure connection truncated
      (<a class="moz-txt-link-freetext" href="https://mycomp:53239">https://mycomp:53239</a>)</tt>" ).&nbsp; I looked in the windows event
    logs for the VisualSVN Server events, and turned out there were
    permission problems.&nbsp; I changed the permissions on the corresponding
    file in the repo/db/revs file to match all the other files in there
    (it must have gotten corrupted too), and now i'm running great.<br>
    <br>
    Hope someone can benefit from my experience.<br>
    <br>
    allie<br>
    <br>
    <div class="moz-cite-prefix">On 11/9/2012 3:14 PM, Alexander Shenkin
      wrote:<br>
    </div>
    <blockquote cite="mid:509D6414.5010...@shenkin.org" type="cite">
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      Hello Folks,<br>
      <br>
      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").<br>
      <br>
      I then ran svnadmin verify, and got the following:<br>
      <blockquote><tt>...</tt><br>
        <tt>* Verified revision 2433.</tt><br>
        <tt>* Verified revision 2434.</tt><br>
        <tt>* Verified revision 2435.</tt><br>
        <tt>svnadmin: E160004: Revision file (r2436) lacks trailing
          newline</tt><br>
      </blockquote>
      Looking online seems to indicate that this might have to do with
      commits &gt; 4GB, though that was an old problem.&nbsp; Given that more
      than 1 file was problematic in the server manager, I figure there
      might be more than one corrupted revision.&nbsp; The damaged files
      aren't critical and haven't changed since being committed for the
      first time.&nbsp; I have working copies of them.<br>
      <br>
      Any thoughts about how I might go about repairing the repo?<br>
      <br>
      Thanks,<br>
      Allie<br>
      <br>
      VisualSVN Server 2.5.2<br>
      svn 1.7.7<br>
      Win 7 Pro x64 SP1<br>
      TortoiseSVN 1.7.10<br>
    </blockquote>
    <br>
  </body>
</html>

--------------010400030304080601020200--