On Mon, Nov 01, 2004 at 12:30:47PM -0800, Alan Wood wrote: > Call Trace: > [<f2ef209e>] query_locks+0x6f/0xad [dlm] > [<f2ef133d>] dlm_query+0x155/0x238 [dlm] > [<f2b79169>] get_conflict_global+0x104/0x2ae [lock_dlm] > [<f2b7905d>] query_ast+0x0/0x8 [lock_dlm] > [<0227c989>] release_sock+0xa5/0xab > [<f2b794c2>] lm_dlm_plock_get+0xcb/0x10f [lock_dlm] > [<f314b4e1>] do_plock+0xc2/0x171 [gfs] > [<f314b5d4>] gfs_lock+0x44/0x52 [gfs] > [<f314b590>] gfs_lock+0x0/0x52 [gfs] > [<02170571>] fcntl_getlk64+0x75/0x12e > [<02170841>] fcntl_setlk64+0x217/0x221 > [<0216c7e0>] sys_fcntl64+0x4d/0x7b This is a kernel oops in the dlm which is always wrong regardless of what you try to do. There have been a lot of changes recently in the area of plocks (where this oopsed) so you should update from cvs, retry and let us know if there's still a problem. -- Dave Teigland <teigland@xxxxxxxxxx>
