How can I prevent TortoiseSVN database locking up?
up vote
1
down vote
favorite
I have a Windows 7 PC with the latest TortoiseSVN version (1.11.0 x64). Almost every time I want to commit changes to the server, I get the following error:
Commit failed (details follow):
Failed to load properties: sqlite[S5]: database is locked
Error unlocking locked dirs (details follow): sqlite[S5]: database is locked
Another process is blocking the working copy database, or the underlying filesystem does
not support file locking; if the working copy is on a network filesystem, make sure file
locking has been enabled on the file server.
It's easy to fix - I just go to the project root folder, do an SVN cleanup, and then the commit works fine. However, if I want to commit again a few minutes after that, it will most likely fail again and force me to do another cleanup. It gets really annoying.
Is there any way I can prevent these locks from happening? Any settings I can change on TortoiseSVN, or something?
A few more details:
- Both my SVN projects and TortoiseSVN itself are placed in my local HDD (no network filesystem), and their folders are excluded from the antivirus software.
- The working copy folder is not network shared (nor locally, I'm the only user on that PC).
- I don't have Dropbox, Google Drive or any other cloud software sync'ing the folder, either.
- It's specific to TortoiseSVN, I never get this error when I commit my changes from Eclipse.
- I really don't think it's a TortoiseSVN bug though, I recently updated from version 1.9.6 to 1.11.0 and both had the same issue, if this really was a bug it surely would have been fixed... right? :)
- I'm the only developer currently working with the projects (it's not an issue of my local database being out of date, or existing conflicts).
svn tortoisesvn
add a comment |
up vote
1
down vote
favorite
I have a Windows 7 PC with the latest TortoiseSVN version (1.11.0 x64). Almost every time I want to commit changes to the server, I get the following error:
Commit failed (details follow):
Failed to load properties: sqlite[S5]: database is locked
Error unlocking locked dirs (details follow): sqlite[S5]: database is locked
Another process is blocking the working copy database, or the underlying filesystem does
not support file locking; if the working copy is on a network filesystem, make sure file
locking has been enabled on the file server.
It's easy to fix - I just go to the project root folder, do an SVN cleanup, and then the commit works fine. However, if I want to commit again a few minutes after that, it will most likely fail again and force me to do another cleanup. It gets really annoying.
Is there any way I can prevent these locks from happening? Any settings I can change on TortoiseSVN, or something?
A few more details:
- Both my SVN projects and TortoiseSVN itself are placed in my local HDD (no network filesystem), and their folders are excluded from the antivirus software.
- The working copy folder is not network shared (nor locally, I'm the only user on that PC).
- I don't have Dropbox, Google Drive or any other cloud software sync'ing the folder, either.
- It's specific to TortoiseSVN, I never get this error when I commit my changes from Eclipse.
- I really don't think it's a TortoiseSVN bug though, I recently updated from version 1.9.6 to 1.11.0 and both had the same issue, if this really was a bug it surely would have been fixed... right? :)
- I'm the only developer currently working with the projects (it's not an issue of my local database being out of date, or existing conflicts).
svn tortoisesvn
1
The working copy is on a network share, is it?
– bahrep
Nov 9 at 19:27
I wish, at least it would explain the problem! But no, the folder is not network shared, and I'm the only user with local access to the computer. Also, now that I think of it... I don't have Dropbox, Google Drive or any other software sync'ing the folder. I'll update the question
– AJPerez
Nov 9 at 20:12
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a Windows 7 PC with the latest TortoiseSVN version (1.11.0 x64). Almost every time I want to commit changes to the server, I get the following error:
Commit failed (details follow):
Failed to load properties: sqlite[S5]: database is locked
Error unlocking locked dirs (details follow): sqlite[S5]: database is locked
Another process is blocking the working copy database, or the underlying filesystem does
not support file locking; if the working copy is on a network filesystem, make sure file
locking has been enabled on the file server.
It's easy to fix - I just go to the project root folder, do an SVN cleanup, and then the commit works fine. However, if I want to commit again a few minutes after that, it will most likely fail again and force me to do another cleanup. It gets really annoying.
Is there any way I can prevent these locks from happening? Any settings I can change on TortoiseSVN, or something?
A few more details:
- Both my SVN projects and TortoiseSVN itself are placed in my local HDD (no network filesystem), and their folders are excluded from the antivirus software.
- The working copy folder is not network shared (nor locally, I'm the only user on that PC).
- I don't have Dropbox, Google Drive or any other cloud software sync'ing the folder, either.
- It's specific to TortoiseSVN, I never get this error when I commit my changes from Eclipse.
- I really don't think it's a TortoiseSVN bug though, I recently updated from version 1.9.6 to 1.11.0 and both had the same issue, if this really was a bug it surely would have been fixed... right? :)
- I'm the only developer currently working with the projects (it's not an issue of my local database being out of date, or existing conflicts).
svn tortoisesvn
I have a Windows 7 PC with the latest TortoiseSVN version (1.11.0 x64). Almost every time I want to commit changes to the server, I get the following error:
Commit failed (details follow):
Failed to load properties: sqlite[S5]: database is locked
Error unlocking locked dirs (details follow): sqlite[S5]: database is locked
Another process is blocking the working copy database, or the underlying filesystem does
not support file locking; if the working copy is on a network filesystem, make sure file
locking has been enabled on the file server.
It's easy to fix - I just go to the project root folder, do an SVN cleanup, and then the commit works fine. However, if I want to commit again a few minutes after that, it will most likely fail again and force me to do another cleanup. It gets really annoying.
Is there any way I can prevent these locks from happening? Any settings I can change on TortoiseSVN, or something?
A few more details:
- Both my SVN projects and TortoiseSVN itself are placed in my local HDD (no network filesystem), and their folders are excluded from the antivirus software.
- The working copy folder is not network shared (nor locally, I'm the only user on that PC).
- I don't have Dropbox, Google Drive or any other cloud software sync'ing the folder, either.
- It's specific to TortoiseSVN, I never get this error when I commit my changes from Eclipse.
- I really don't think it's a TortoiseSVN bug though, I recently updated from version 1.9.6 to 1.11.0 and both had the same issue, if this really was a bug it surely would have been fixed... right? :)
- I'm the only developer currently working with the projects (it's not an issue of my local database being out of date, or existing conflicts).
svn tortoisesvn
svn tortoisesvn
edited Nov 9 at 20:15
asked Nov 9 at 13:47
AJPerez
2,21484262
2,21484262
1
The working copy is on a network share, is it?
– bahrep
Nov 9 at 19:27
I wish, at least it would explain the problem! But no, the folder is not network shared, and I'm the only user with local access to the computer. Also, now that I think of it... I don't have Dropbox, Google Drive or any other software sync'ing the folder. I'll update the question
– AJPerez
Nov 9 at 20:12
add a comment |
1
The working copy is on a network share, is it?
– bahrep
Nov 9 at 19:27
I wish, at least it would explain the problem! But no, the folder is not network shared, and I'm the only user with local access to the computer. Also, now that I think of it... I don't have Dropbox, Google Drive or any other software sync'ing the folder. I'll update the question
– AJPerez
Nov 9 at 20:12
1
1
The working copy is on a network share, is it?
– bahrep
Nov 9 at 19:27
The working copy is on a network share, is it?
– bahrep
Nov 9 at 19:27
I wish, at least it would explain the problem! But no, the folder is not network shared, and I'm the only user with local access to the computer. Also, now that I think of it... I don't have Dropbox, Google Drive or any other software sync'ing the folder. I'll update the question
– AJPerez
Nov 9 at 20:12
I wish, at least it would explain the problem! But no, the folder is not network shared, and I'm the only user with local access to the computer. Also, now that I think of it... I don't have Dropbox, Google Drive or any other software sync'ing the folder. I'll update the question
– AJPerez
Nov 9 at 20:12
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53226943%2fhow-can-i-prevent-tortoisesvn-database-locking-up%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The working copy is on a network share, is it?
– bahrep
Nov 9 at 19:27
I wish, at least it would explain the problem! But no, the folder is not network shared, and I'm the only user with local access to the computer. Also, now that I think of it... I don't have Dropbox, Google Drive or any other software sync'ing the folder. I'll update the question
– AJPerez
Nov 9 at 20:12