Return-Path: Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: (qmail 26944 invoked from network); 6 Jan 2011 14:38:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Jan 2011 14:38:49 -0000 Received: (qmail 79725 invoked by uid 500); 6 Jan 2011 14:38:48 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 79427 invoked by uid 500); 6 Jan 2011 14:38:47 -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 Delivered-To: moderator for users@subversion.apache.org Received: (qmail 52540 invoked by uid 99); 6 Jan 2011 02:49:09 -0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Subject: Re: svn: REPORT request failed on '/svn/!svn/bc/20890' Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=windows-1252 From: Ryan Schmidt In-Reply-To: <000001cbace3$5db8fff0$192affd0$@com> Date: Wed, 5 Jan 2011 20:48:34 -0600 Cc: Content-Transfer-Encoding: quoted-printable Message-Id: <18FADCF7-2B60-406F-9020-F10FF0088256@ryandesign.com> References: <000001cbace3$5db8fff0$192affd0$@com> To: zhangfan X-Mailer: Apple Mail (2.1082) X-Df-Sender: 368818 X-Virus-Checked: Checked by ClamAV on apache.org On Jan 5, 2011, at 08:18, zhangfan wrote: > I am using svn1.6.3. I put all source code and documents of = our team into one repo. It works great for two years until last month. = Now when I run =91svn log http://192.168.0.3:907/svn=92 (where = 192.168.0.3 is our server=92s address), svn returns =91svn: REPORT = request failed on '/svn/!svn/bc/20890' after returned some log = information. You say it does return some log information, but not all of it? Sounds = like maybe a corrupted revision in the repository. You could try running = "svnadmin verify". There are also some other tools you could run = depending on whether it's a BDB or FSFS repository.