Subversion fsfs migration
Par jd le vendredi, décembre 31 2004, 11:45 - University - Lien permanent
Today I discovered that a new storage backend is implemented in Subversion: fsfs.
This seems to be the ultimate solution against the problems I had with the repository I used with my friends at University: databases crashes and permissions problems.
I just migrated the repository, this is very simple:
netu lib/svn # svnadmin dump iup > iup.svn.dump [...] netu lib/svn # svnadmin create --fs-type fsfs iup-fsfs netu lib/svn # svnadmin load iup-fsfs < iup.svn.dump [...] netu lib/svn # mv iup iup.old netu lib/svn # mv iup-fsfs iup netu lib/svn # chown -R acid.iup iup && chmod -R g+w iup
Done.
Commentaires
Thanks for the quick instructions on the migration. After seeing how simple it was (and after yet another database lockup last night), I opted to do the same today. No problems.
Hey, thanks for that. I just switched my repositories using your technique.
No more stupid post-install hooks to keep BDB happy!
Hey, thanks a lot for the simple instructions. I switched my repositories without any issues.
Just wanted to throw in my thanks as well. Just switched, and it instantly solved all my Trac/Subversion/BDB problems. Nice!
Thanks a lot for the simple instructions!!! my svn developers (that's me and a friend) now live happier.
Hi,
At first, thanks a lot for the useful hint and your hard work for Debian project!
It seems that `svnadmin dump` command doesn't dump your hooks and conf. Please see <a href="http://subversion.tigris.org/faq.html#bdb-fsfs-convert">SVN FAQ</a>, if you don't believe me
So, my advice is: compare conf for both back-ends and copy your old BDB hooks to new FSFS repository.
P.
Fil des commentaires de ce billet