Red Hat Bugzilla – Bug 437507
DLM_LSFL_TIMEWARN does not appear to work.
Last modified: 2009-04-16 19:03:15 EDT
Description of problem:
I created a new lockspace "timewarn" with the DLM_LSFL_TIMEWARN flag set and
attempted to get a lock which I knew would be placed on the wait queue with the
timeout value set to 100 using dlm_ls_lockx() interface.
I'm still waiting for the ast for that lock...
If I watch the dlm_tool lockdump output I see both locks there:
[root@marathon-01 dlm]# dlm_tool lockdump timeout
id 00080001 gr EX rq NL pid 3284 master 0 "timeouttest"
id 02440001 gr IV rq EX pid 3284 master 0 "timeouttest"
I was expecting an ast for lock 02440001 to be sent with an sb_status of
something other than 0. That ast is never sent.
Version-Release number of selected component (if applicable):
Not a bug -- Needed to use the LKF_TIMEOUT in the dlm_lockx() flags. The
example in the 'Programming Locking Applications' showed the flags == 0.
This works as expected if LKF_TIMEOUT is set.