httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 44865] mod_dav' s lock database becomes consistently corrupt
Date Fri, 25 Apr 2008 17:25:00 GMT

--- Comment #6 from Jeremy Orem <>  2008-04-25 10:25:00 PST ---
It doesn't look like the lock database is being recreated.  I watched the lock
directory for about a minute with inotify.  Results:

     43 lockdb.dir IN_CLOSE_WRITE
     43 lockdb.dir IN_OPEN
     46 lockdb.dir IN_ACCESS
     46 lockdb.pag IN_CLOSE_WRITE
     46 lockdb.pag IN_OPEN
    187 lockdb.pag IN_MODIFY
    243 lockdb.pag IN_ACCESS

I was able to trigger

[Fri Apr 25 10:24:16 2008] [error] [client] (2)No such file or
directory: The lock database was found to be corrupt. An indirect lock's direct
lock could not be found.  [500, #402]

several times while watching.  

The strange thing is that it seems to only become corrupt for certain
directories.  For example even though locking
/user/05c3d5e2202a7f92edddfb4753c5fa771758daeb/ causes 500 errors I can lock a
different directory with no problems.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message