database is locked error

Asked by deadmeat

Hi,

I installed the latest TimeVault deb package on my Ubuntu 7.10 system.

The config window ran fine the first time but will not appear again. I have rebooted the system but I still see the following error.
Note that I have logged into a terminal window as root to try to run timevault-config.

root</>/usr/bin/timevault-config

(timevault-config:5701): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.
Traceback (most recent call last):
  File "/usr/bin/timevault-config", line 31, in <module>
    configgui.MainDlg().Show()
  File "/usr/lib/python2.5/site-packages/TimeVault/configgui.py", line 241, in Show
    self.CheckDBVersion()
  File "/usr/lib/python2.5/site-packages/TimeVault/configgui.py", line 235, in CheckDBVersion
    if not db.Open():
  File "/usr/lib/python2.5/site-packages/TimeVault/database.py", line 107, in Open
    self.Create(0)
  File "/usr/lib/python2.5/site-packages/TimeVault/database.py", line 78, in Create
    result.Exec(sql)
  File "/usr/lib/python2.5/site-packages/TimeVault/database.py", line 42, in Exec
    self.cursor.execute(*args)
pysqlite2.dbapi2.OperationalError: database is locked

Any suggestions would be much appreciated.

Question information

Language:
English Edit question
Status:
Solved
For:
TimeVault Edit question
Assignee:
No assignee Edit question
Solved by:
deadmeat
Solved:
Last query:
Last reply:
Revision history for this message
deadmeat (bill-roberts) said :
#1

More information:

The locking problem only seems to occur when I set my Snapshots Root Directory
to be a directory on a filesystem mounted from our Samba server. i.e. a filesystem
mounted using /sbin/mount.cifs The catalog, internal and pending directories all
get created and the catalog.db file is created, but the locking problem stops
everything from working.

It would be great to be able to run TimeVault and have it write to a disk mounted
from a Samba server.

Maybe this has gone from a bug report to a feature request?

Revision history for this message
Yves Marcoz (yves-marcoz) said :
#2

I had the same issue with the database mounted on a Samba share. I found this thread dealing with the underlying problem:
http://lists.samba.org/archive/linux-cifs-client/2006-November/001584.html
Mounting the Samba share with the option nobrl fixed it for me.

Revision history for this message
deadmeat (bill-roberts) said :
#3

Thanks Yves, you were absolutley correct. Adding the nobrl option to my mount.cifs has allowed Timevault to work for me.