Restrice folder access from TortoiseSVN

[kfank]

I'm running a linux VM under a windows host.  I've checked out a subversion source tree to a shared folder (between host and guest) from within the guest OS.  TortoiseSVN on the host also sees this source tree, but there is apparently a conflict caused by the two systems interacting with the source tree.  This results in I/O errors or corruption of the database files:

svn: E200030: sqlite[S10]: disk I/O error

Is there any way to declare a folder (and all its subfolders) off-limits from TortoiseSVN to avoid this conflict?

[Daniel Sahlberg]

lördag 25 mars 2023 kl. 06:54:43 UTC+1 skrev kurtbu...@gmail.com:

I'm running a linux VM under a windows host.  I've checked out a subversion source tree to a shared folder (between host and guest) from within the guest OS.  TortoiseSVN on the host also sees this source tree, but there is apparently a conflict caused by the two systems interacting with the source tree.  This results in I/O errors or corruption of the database files:

svn: E200030: sqlite[S10]: disk I/O error

Depending on your hypervisor (you don't mention if you are using WSL or any of the more "complete" hypervisor solutions) there may be limitation on the support for file locking on the shared folder. Check for example https://github.com/microsoft/WSL/issues/4689 and also the FAQ item regarding WCsa on shared folders https://www.tortoisesvn.net/faq.html#wconshare

If you want further help, please give a little more details regarding your VM setup (for example if the folder where you put the WC is shared from the host to the guest or the opposite).

Is there any way to declare a folder (and all its subfolders) off-limits from TortoiseSVN to avoid this conflict?

 

Not that I know of - however by default TortoiseSVN is only touching a folder when you browse to it in Explorer.

Kind regards,

Daniel

[kfank]

If you want further help, please give a little more details regarding your VM setup (for example if the folder where you put the WC is shared from the host to the guest or the opposite).

I'm using a Vagrant VM under Virtualbox. 

Is there any way to declare a folder (and all its subfolders) off-limits from TortoiseSVN to avoid this conflict?

 

Not that I know of - however by default TortoiseSVN is only touching a folder when you browse to it in Explorer.

How can I submit this as a feature request? 

 

[Daniel Sahlberg]

fredag 31 mars 2023 kl. 00:50:57 UTC+2 skrev kurtbu...@gmail.com:

If you want further help, please give a little more details regarding your VM setup (for example if the folder where you put the WC is shared from the host to the guest or the opposite).

I'm using a Vagrant VM under Virtualbox. 

I assume you run the SVN command getting the error from within the virtual machine. Is the folder where you have stored the working copy mounted in the VM from the host or is it a folder that is purely within the VM (ie residing within the virtual harddisk)?

If it is stored on a folder on the host that you have mounted within the VM, then I don't think the problem lies with TortoiseSVN touching the folder but rather that you run into problems because the "shared folder" functionality of VirtualBox don't have the required file locking semantics. The best way to prove this is probably to kill Explorer.exe and any TortoiseProc.exe processes and retry the operation from within the VM. If you still have problems, then it is not related to TortoiseSVN. (When you kill Explorer.exe you will loose the start menu so make sure you've started any programs, for example the VM console, before the test. You can restart Explorer.exe from the Task Manager when the experiment is done).

 

Is there any way to declare a folder (and all its subfolders) off-limits from TortoiseSVN to avoid this conflict?

 

Not that I know of - however by default TortoiseSVN is only touching a folder when you browse to it in Explorer.

How can I submit this as a feature request? 

Here is a good place but we need to make sure it is actually caused by TortoiseSVN, preferably in a way so the developers can reproduce the issue.

The "10" in the [S10] part of your error message is an SQLite error number. It indicates an IO error https://www.sqlite.org/rescode.html#ioerr

Kind regards,

Daniel