Bug 669535

Summary:	Regression: svnadmin hotcopy throws error
Product:	Red Hat Enterprise Linux 5	Reporter:	Troels Arvin <troels>
Component:	subversion	Assignee:	Joe Orton <jorton>
Status:	CLOSED CURRENTRELEASE	QA Contact:	qe-baseos-daemons
Severity:	low	Docs Contact:
Priority:	high
Version:	5.6	CC:	azelinka, syeghiay
Target Milestone:	rc	Keywords:	Regression, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	808010 (view as bug list)		Environment:
Last Closed:	2013-09-23 11:16:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	681522

Description Troels Arvin 2011-01-13 21:58:31 UTC

Description of problem:
Part of the news in RHEL 5.6 is a newer generation of subversion (from version 1.4.2 to version 1.6.11). However, after the upgrade, backups using the "svnadmin hotcopy" yield an error message. The resulting backup _seems_ to be OK, but I'm not completely sure.

Version-Release number of selected component (if applicable):
subversion-1.6.11-7.el5

How reproducible:
Every time, after upgrading from RHEL 5.5 to 5.6.

Steps to Reproduce:
1. Given a RHEL 5.5 installation with at least one working Subversion repository.
2. Upgrade to RHEL 5.6.
3. Run the "svnadmin hotcopy" command.
  
Actual results:
svnadmin: Can't open file 'REPONAME/db/fsfs.conf': No such file or directory

Expected results:
Silence.

Additional info:
Putting the error message in a search engine reveals that it's not an unknown problem: It seems that the problem was introduced in Subversion v. 1.6.11 and was probably fixed in 1.6.13 by this change:
http://svn.apache.org/viewvc?view=revision&revision=980811

I think that RHEL 5.6's Subversion should either be upgraded to version 1.6.13 (or later), or someone should consider if the isolated change in revision 980811 is safe to back-port.

Comment 1 Joe Orton 2011-01-14 11:46:09 UTC

Thanks for the report, and sorry about the regression.  

That looks fine to backport.  It looks like a simple workaround would be to run:

  touch REPONAME/db/fsfs.conf

before the hotcopy for older repos, though I haven't verified that.

Comment 7 Troels Arvin 2011-03-15 22:17:24 UTC

I believe that this bug can be closed, now that RHSA-2011:0327 is out.

Comment 8 Joe Orton 2011-03-16 08:54:59 UTC

Thanks - in fact for internal purposes we need to keep this bug open, since the released erratum comes from a different development branch.