I'm investigating setting up a replacement SVN server (Apache mod_dav_svn), but would ideally like to store the actual repositories on a remote Samba share.
Edit: to clarify, client access will still go through the Apache front end, NOT directly to the repository.
Are there any reasons why this would be a (really) bad idea?
My main concern is data integrity (i.e. from files being sent to the Apache server, and then written from that server to the remote storage - especially if any packets get lost), though should the SVN itself guarantee the integrity of data before allowing each actual commit to complete?
One risk identified is that if the network or remote storage goes down, we loose access to the repo, but the network in question has built in resilience, and the remote storage is a SAN (again with resilience) so I'm comfortable with this.
Is there anything else I'm missing?