On Nov. 5, Juergen Bock wrote (in a message titled
"32/64bit locking problem with 2.2.2") that he was seeing
a 32/64bit locking error in his logs.
I have also seen this problem. I have a little more information
that indicates that this behavior started after samba version
2.2.0a.
Here are the samba versions I have tested:
Samba 2.2.0a (compiled on rh7.1 system with kernel 2.4.5)
Samba 2.2.2 (compiled on rh7.1 system with kernel 2.4.5)
Samba 2.2.2 (compiled on rh7.1 system with kernel 2.4.16)
RedHat systems with kernels:
2.4.5
2.4.16
In all cases, the samba 2.2.0a version works (no locking problems).
In all cases, both compiles of samba 2.2.2 fail (locking problems).
The error does seem to follow samba (something must have changed
between 2.2.0a and 2.2.2 to start driving this behavior.) The
behavior on the windows machine is that it is unable to open the
file.
My scenario:
A windows terminal server box (NT4.0 TSE) maps a drive to
\\sambaserver\myhome each time a user logs in. "myhome" is a
samba share of the user's NIS home over NFS. This makes the
sambaserver the client.
The particular NFS server used in this test was Solaris 2.6, but
we have Linux and HPUX servers as well. This was in a production
environment, so I rolled back as soon as I saw the errors, leaving
Solaris 2.6 as positively known to produce this error, others
unknown.
Here is a copy of a typical error log:
[2001/12/13 09:24:48, 2] smbd/open.c:open_file(214)
ig opened file consult/gerotor/390h/stage2/pp/pow-pt/390h-compare2.1-adapt.ppt
read=Yes
write=Y
es (numopen=1)
[2001/12/13 09:24:48, 0] locking/posix.c:posix_fcntl_lock(668)
posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1
returned
[2001/12/13 09:24:48, 0] locking/posix.c:posix_fcntl_lock(670)
an Invalid argument error. This can happen when using 64 bit lock offsets
[2001/12/13 09:24:48, 0] locking/posix.c:posix_fcntl_lock(671)
on 32 bit NFS mounted file systems.
[2001/12/13 09:24:48, 2] smbd/close.c:close_normal_file(206)
ig closed file consult/gerotor/390h/stage2/pp/pow-pt/390h-compare2.1-adapt.ppt
(numopen=0)
I am hopeful that somebody can pinpoint the cause of this error.
I could test against HPUX and Linux additionally, if that is of
interest.
cheers,
mtw
