samba - May 2002 - fcntl_lock problem: samba 2.2.3a, kernel 2.2.19

I'm trying to solve a roaming profile problem which manifests as a locking
error during Win2K logout with roaming profiles enabled. Level 3 debug
tells me:

[2002/05/30 11:59:58, 2] smbd/open.c:open_file(213)
  markk opened file markk/ntuser.ini read=Yes write=Yes (numopen=1)
[2002/05/30 11:59:58, 3] smbd/process.c:process_smb(860)
  Transaction 1449 of length 75
[2002/05/30 11:59:58, 3] smbd/process.c:switch_message(667)
  switch message SMBlockingX (pid 2570)
[2002/05/30 11:59:58, 3] lib/util.c:fcntl_lock(1287)
  fcntl_lock: fcntl lock gave errno 75 (Value too large for defined data 
type)
[2002/05/30 11:59:58, 3] lib/util.c:fcntl_lock(1308)
  fcntl_lock: lock failed at offset 0 count 9223372036854775808 op 13 type 
1 (Value too large for defined data type)
[2002/05/30 11:59:58, 3] smbd/blocking.c:push_blocking_lock_request(120)
  push_blocking_lock_request: lock request length=75 blocked with expiry 
time -1 (+-1) for fnum = 6154, name = markk/ntuser.ini
[2002/05/30 12:00:08, 3] smbd/sec_ctx.c:set_sec_ctx(313)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2002/05/30 12:00:08, 3] smbd/sec_ctx.c:set_sec_ctx(313)
  setting sec ctx (5001, 5001) - sec_ctx_stack_ndx = 0
[2002/05/30 12:00:08, 3] smbd/sec_ctx.c:set_sec_ctx(319)
  2 user groups: 
  5001 500 
[2002/05/30 12:00:08, 3] lib/util.c:fcntl_lock(1287)
  fcntl_lock: fcntl lock gave errno 75 (Value too large for defined data 
type)
[2002/05/30 12:00:08, 3] lib/util.c:fcntl_lock(1308)
  fcntl_lock: lock failed at offset 0 count 9223372036854775808 op 13 type 
1 (Value too large for defined data type)
[2002/05/30 12:00:08, 3] smbd/error.c:error_packet(91)
  error string = Value too large for defined data type
[2002/05/30 12:00:08, 3] smbd/error.c:error_packet(99)
  error packet at smbd/blocking.c(179) cmd=36 (SMBlockingX) 
NT_STATUS_LOCK_NOT_GRANTED

I note that 9223372036854775808 == 0x8000000000000000, so this isn't a 
genuine region locking call.  Shouldn't this lock be filtered out before 
fcntl_lock() is called?

I've found a workaround: setting "posix locking = no" for the
Profiles
share hides the problem quite effectively.

I can provide more information if anyone needs help to find the but.

-- 

Charlie