recovery messes-up repository perms

Greetings.

One of the users of a repository that I admin just got an error telling
me to run recovery on the repository. I'd like to know what caused that,
but I ran it. What causes that?

Now, the perms in the db directory are wrong for sharing with a group.

root@tux:/home/svn# ls -l db
total 18108
-rw-rw---- 1 root svn 1738 Jun 4 14:18 DB_CONFIG
-rw-r--r-- 1 root svn 8192 Jun 26 21:17 __db.001
-rw-r--r-- 1 root svn 270336 Jun 26 21:17 __db.002
-rw-r--r-- 1 root svn 327680 Jun 26 21:17 __db.003
-rw-r--r-- 1 root svn 737280 Jun 26 21:17 __db.004
-rw-r--r-- 1 root svn 16384 Jun 26 21:17 __db.005
-rw-rw---- 1 root svn 65536 Jun 26 21:17 changes
-rw-rw---- 1 root svn 8192 Jun 26 21:17 copies
-rw-r--r-- 1 msoulier svn 1048510 Jun 24 19:50 log.0000000030
-rw-r--r-- 1 msoulier svn 752212 Jun 26 21:17 log.0000000031
-rw-rw---- 1 root svn 53248 Jun 26 21:17 nodes
-rw-rw---- 1 root svn 65536 Jun 26 21:17 representations
-rw-rw---- 1 root svn 8192 Jun 26 21:17 revisions
-rw-rw---- 1 root svn 15745024 Jun 26 21:17 strings
-rw-rw---- 1 root svn 24576 Jun 26 21:17 transactions
-rw-rw---- 1 root svn 8192 Jun 26 21:17 uuids

Why did recover remove write access for group? All the developers are in
the svn group for that very reason, which is recommended in the SVN FAQ.

We're using svn over ssh.

Thanks,
Mike

-- 
Michael P. Soulier <msoulier@digitaltorque.ca>
The major advances in civilization are processes that all but wreck the
societies in which they occur.
-- Albert North Whitehead