Den tis 18 juni 2024 kl 17:49 skrev Johnston, Tim < tim.johns...@christiedigital.com>:
> We are using SVN 1.7 repositories which are checked out to a Linux file > server. Users access their files via TortoiseSVN (1.7.15, which is also > built against SVN 1.7.x), either via CIFS or NFS. > That is a really old version, with an equally old version of SQLite. > > When accessing via CIFS (with the Linux side serving via Samba), we > occasionally encounter SQLite database corruption. My understanding is that > this is caused by differences between the Windows and POSIX locking > implementations (inside libsvn). > I'm not sure if it is Subversion or SQLite that is having the most problems but general wisdom is to not store a working copy on a network share. > > When accessing via the official Windows NFS client (talking to a Linux NFS > server), we are unable to even check out a repository via TortoiseSVN. It > fails immediately with a locking error. > > I find it very difficult to search for this issue, partly because SVN has > an unrelated "file locking" feature, and partly because users have posted > about a number of other simpler SQLite corruption issues with SVN.. > > So my question is this: what is the current state of SVN clients on > Windows, accessing a Linux file share, with respect to file locking / > SQLite etc? > Are there options for this problem with newer Windows (Tortoise)SVN client > versions? Or is this problem still the same in the newest versions? > I don't think any significant work has been done towards supporting working copies on network shares. Subversion relies on proper file locking and if this fails (which I assume is the cause of your trouble) then all bets are off. SQLite goes quite far in recommending to use another database engine if over-the-network functionality is required: https://www.sqlite.org/useovernet.html These are the two FAQ items I can find mentioning problems storing a working copy / sqlite database on a network share: https://tortoisesvn.net/faq.html#wconshare https://www.sqlite.org/faq.html#q5 Our own FAQ suggests that storing a working copy on an NFS share should be fine, but I presume the Windows NFS client is not as well behaved as Unix NFS clients. https://subversion.apache.org/faq.html#nfs > > Any recommendations would be appreciated! > Why do you need to store the working copy on a network share? Can you adjust your workflow to make sure every user has their own working copy, stored on local disk? Kind regards, Daniel
