I am using 3.0.20b. I understand that these messages show up because
client sends a lock request that is not on the valid range.
[2005/12/01 15:16:25, 0] locking/posix.c:posix_fcntl_lock(667)
an Invalid argument error. This can happen when using 64 bit lock offsets
[2005/12/01 15:16:25, 0] locking/posix.c:posix_fcntl_lock(668)
on 32 bit NFS mounted file systems.
[2005/12/01 15:16:26, 0] locking/posix.c:posix_fcntl_lock(666)
posix_fcntl_lock: WARNING: lock request at offset 0, length 349 returned
[2005/12/01 15:16:26, 0] locking/posix.c:posix_fcntl_lock(667)
an Invalid argument error. This can happen when using 64 bit lock offsets
[2005/12/01 15:16:26, 0] locking/posix.c:posix_fcntl_lock(668)
Searching the archive, I discovered that this should have been fixed
in the newer version and I should look for this piece of code in
posix.c: (I found this)
/*
* We must truncate the count to less than max_positive_lock_offset.
*/
if (u_count & ~((SMB_BIG_UINT)max_positive_lock_offset))
count = max_positive_lock_offset;
/*
any idea?