Got a bit of an odd setup, perhaps.
I have put local checkouts of my SVN repository in Dropbox folders (Windows 11 machine).
So basically at any machine I work, I have the last edits whether they've been sent to SVN server or not. Plus, I can keep un-versioned documents and other non-code in the same directories, and they will be synced across machines, too.
It worked very well for me. Until I started to use Windows Subsystem for Linux 2 .
Nowadays, while I work on code from inside WSL OK, whenever I need to commit or update to/from SVN server, in about 70% of cases SVN will complain of Disk I/O error and occasionally corrupt its database. If you re-run commit, it might work. If you do svn cleanup and recommit, it might work or not.
This is usually resolved easily by doing the SVN commit/updates from Windows explorer side (I use TortoiseSVN), which work fine, and from which I can cleanup/repair database as well.
So it appears something to do with how WSL plays with things and how it or Dropbox deals with temporary files and file locking(? i presume).
Anyone else experienced something similar to this, with regard to Dropbox and/or WSL?
Any ideas or solutions appreciated.