trac locks database and causes potential corruption when using apache on windows
|Reported by:||anonymous||Owned by:||Christopher Lenz|
|Severity:||critical||Keywords:||svn database lock|
Description (last modified by )
Here's the description from one of our developers…
Trac is causing Subversion database corruption and I had to disable it. Even though Trac only reads database, every read operation locks it, like it's going to do transaction. That doesn't jive well with normal svn client that uses svn_dav Apache module to access database. In the end, two different access methods cause DB corruption (we didn't lose anything with nightly backup and incremental dump on commit). I don't expect to re-activate Trac soon (soon=weeks or months).
Edit: This is not a Trac bug, but a Subversion one. Using svn 1.1, and particularly with FSFS, it is no longer an issue. Edit2: Also, to clarify, it was never an issue of corruption, but rather a mere inconvenience due to loss of state in berkeley db. No data has ever been reported lost.
Change History (42)
comment:14 by , 16 years ago
|Summary:||trac locks database and causes potential corruption when using apache → trac locks database and causes potential corruption when using apache on windows|
comment:22 by , 15 years ago
|Status:||closed → reopened|