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_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-09 21:07:52 CEST