Repository Upgrade Problems moving to 1.5

[Scott Palmer <sw...@gmail.com>]

Hello all,

I recently upgraded our server and repository to Subversion 1.5 and there
were a couple hiccups along the way that I thought I would share.  It's
probably my fault for not reading enough documentation ahead of time, but
maybe this post can save someone the same trouble or shed light on a need
for clearer documentation.

The problem is with locks.  When doing the upgrade I decided to do a
dump/load to get the most efficient results possible (sharding the FSFS
database etc.) - I had everyone disconnected anyway so why not take the time
to do it as thoroughly as possible...

Two users had obtained locks on files prior to the update, but when the data
was restored the locks were "lost".  This resulted in another user getting a
lock and modifying a file that should have been locked already by someone
else.  In another case according to my user, "I locked my Design-Debug log
before the SVN upgrade, and then during the upgrade the server lost the lock
status.  So I tried to get the lock again so I could check-in my changes,
and it reverted my log back to what's in the repository, so I lost all my
changes."

I'm trying to get more detailed information of the subversion commands
used.  I believe everyone was using the TortoiseSVN client, though at this
point it doesn't seem to be a client issue to me.

In any case the documentation I read mentioned things like copying over hook
scripts and config files after the dump load... but nothing mentioned an
extra step required to preserve locks.

Regards,

Scott

P.S. please copy me on replies as I am not subscribed to the list.

Re: Repository Upgrade Problems moving to 1.5

[Scott Palmer <sw...@gmail.com>]

On 10-Jul-08, at 5:32 AM, Jonathan Ashley wrote:

>>> ... In another case according to my user, "I
>>> locked my Design-Debug log before the SVN upgrade, and then
>> during the
>>> upgrade the server lost the lock status.  So I tried to get
>> the lock
>>> again so I could check-in my changes, and it reverted my
>> log back to
>>> what's in the repository, so I lost all my changes."
>>>
>>> ...
>>>
>>> In any case the documentation I read mentioned things like copying
>>> over hook scripts and config files after the dump load...
>> but nothing
>>> mentioned an extra step required to preserve locks.
>>
>> You're correct. Locks are not preserved in a dumpfile.
>
> You can however, copy the db/locks folder from your old repository to
> your new one, and everything should work. Assuming FSFS of course.

Thanks, I'll remember that for next time.

> Well... it worked for me anyway. I should point out that I also kept
> the same URL to access the repository (i.e. the server name did not
> change) and the same repository UUID. I don't know if changes here
> could have caused problems.

Load into an empty repo preserves the UUID so that shouldn't be a  
problem for my case.

> I would be surprised if the client quietly reverted the changed file
> and caused changes to be lost. Are you sure that your user didn't
> accidentally do that?


I was also very surprised.  But that is the claim.  They say all they  
did was use TortoiseSVN to "Get Lock" on the file.  It makes no sense  
to me.

Regards,

Scott

RE: Repository Upgrade Problems moving to 1.5

[Jonathan Ashley <jo...@praxis-his.com>]

> > The problem is with locks.  When doing the upgrade I
> decided to do a
> > dump/load to get the most efficient results possible (sharding the
> > FSFS database etc.) - I had everyone disconnected anyway so why not
> > take the time to do it as thoroughly as possible...
> >
> > Two users had obtained locks on files prior to the update, but when
> > the data was restored the locks were "lost".  This resulted
> in another
> > user getting a lock and modifying a file that should have
> been locked
> > already by someone else.  In another case according to my user, "I
> > locked my Design-Debug log before the SVN upgrade, and then
> during the
> > upgrade the server lost the lock status.  So I tried to get
> the lock
> > again so I could check-in my changes, and it reverted my
> log back to
> > what's in the repository, so I lost all my changes."
> >
> > I'm trying to get more detailed information of the
> subversion commands
> > used.  I believe everyone was using the TortoiseSVN client,
> though at
> > this point it doesn't seem to be a client issue to me.
> >
> > In any case the documentation I read mentioned things like copying
> > over hook scripts and config files after the dump load...
> but nothing
> > mentioned an extra step required to preserve locks.
>
> You're correct. Locks are not preserved in a dumpfile.

You can however, copy the db/locks folder from your old repository to
your new one, and everything should work. Assuming FSFS of course.

Well... it worked for me anyway. I should point out that I also kept
the same URL to access the repository (i.e. the server name did not
change) and the same repository UUID. I don't know if changes here
could have caused problems.

I would be surprised if the client quietly reverted the changed file
and caused changes to be lost. Are you sure that your user didn't
accidentally do that?

regards,
--
Jon Ashley


This email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, disclosure, copying or distribution or any action taken or omitted to be taken in reliance on it is strictly prohibited. If you have received this email in error please contact the sender. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Praxis. 

Although this email and any attachments are believed to be free of any virus or other defect, no responsibility is accepted by Praxis or any of its associated companies for any loss or damage arising in any way from the receipt or use thereof. The IT Department at Praxis can be contacted at it.support@praxis-his.com.

Praxis High Integrity Systems Ltd:

Company Number: 3302507, registered in England and Wales

Registered Address: 20 Manvers Street, Bath. BA1 1PX

VAT Registered in Great Britain: 682635707


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Repository Upgrade Problems moving to 1.5

[Ryan Schmidt <su...@ryandesign.com>]

On Jul 9, 2008, at 10:52, Scott Palmer wrote:

> I recently upgraded our server and repository to Subversion 1.5 and  
> there were a couple hiccups along the way that I thought I would  
> share.  It's probably my fault for not reading enough documentation  
> ahead of time, but maybe this post can save someone the same  
> trouble or shed light on a need for clearer documentation.
>
> The problem is with locks.  When doing the upgrade I decided to do  
> a dump/load to get the most efficient results possible (sharding  
> the FSFS database etc.) - I had everyone disconnected anyway so why  
> not take the time to do it as thoroughly as possible...
>
> Two users had obtained locks on files prior to the update, but when  
> the data was restored the locks were "lost".  This resulted in  
> another user getting a lock and modifying a file that should have  
> been locked already by someone else.  In another case according to  
> my user, "I locked my Design-Debug log before the SVN upgrade, and  
> then during the upgrade the server lost the lock status.  So I  
> tried to get the lock again so I could check-in my changes, and it  
> reverted my log back to what's in the repository, so I lost all my  
> changes."
>
> I'm trying to get more detailed information of the subversion  
> commands used.  I believe everyone was using the TortoiseSVN  
> client, though at this point it doesn't seem to be a client issue  
> to me.
>
> In any case the documentation I read mentioned things like copying  
> over hook scripts and config files after the dump load... but  
> nothing mentioned an extra step required to preserve locks.

You're correct. Locks are not preserved in a dumpfile.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org