samba - Dec 2002 - Strange locking errors with LabView under Samba 2.2.7 and HP-UX 1 1.11

Hello All,

I recently upgraded one of my HP-UX servers from Samba 2.2.4 to 2.2.7.
Since that time, I have noticed that disk activity on the file system where
the Samba var directory is kept seems to be higher than I would expect.  We
have now begun to experience a problem with PC clients running National
Instruments' LabView software, installed on a Samba share.  When any PC
client tries to execute it, disk utilization goes to 100% according to HP's
Glance performance monitor, with nearly all activity being in the
aforementioned file system containing the Samba var files and being caused
by the smbd for the client running LabView.  Using Glance to look at open
files, I found that the only open file located in the Samba var file system
is the smbd log file, and it is filled with messages like this:

[2002/12/19 17:47:17, 0] locking/posix.c:(660)

  posix_fcntl_lock: WARNING: lock request at offset 0, length
9223372036854779000 returned

[2002/12/19 17:47:17, 0] locking/posix.c:(662)

  an Invalid argument error. This can happen when using 64 bit lock offsets

[2002/12/19 17:47:17, 0] locking/posix.c:(663)

  on 32 bit NFS mounted file systems.

[2002/12/19 17:47:17, 0] locking/posix.c:(677)

  Count greater than 31 bits - retrying with 31 bit truncated length.

[2002/12/19 17:47:17, 0] locking/posix.c:(660)

  posix_fcntl_lock: WARNING: lock request at offset 0, length
9223372036854779000 returned

[2002/12/19 17:47:17, 0] locking/posix.c:(662)

  an Invalid argument error. This can happen when using 64 bit lock offsets

[2002/12/19 17:47:17, 0] locking/posix.c:(663)

  on 32 bit NFS mounted file systems.

[2002/12/19 17:47:17, 0] locking/posix.c:(677)

over and over again.  I have log level set to 1, with a different log for
each client.  After several minutes, LabView finally loads and things settle
back down.  Any ideas as to what is happening?  The log mentions NFS, but
the directories containing LabView are local to my system and are exported
by Samba only, not NFS.

My copy of Samba was compiled here using HP's ANSI C compiler under HP-UX
11.11.  I ran configure with very few options, just to set the prefix and to
set "--with-utmp".  None of these problems occurred under Samba 2.2.4,
and I
haven't yet had a chance to try out 2.2.7a to see if there's any
difference.
The problem occurs when running LabView with both NT4 and W2K clients.  With
our holiday shutdown almost here, I hope to get a chance to try 2.2.7a
sometime tomorrow.

Thanks in advance for any assistance!

Dave Windsor 
AdW/MOE2.12 
Team Leader, Test Systems Engineering 
Robert Bosch Corporation 
Anderson, SC, USA 
email: <mailto:Dave.Windsor@us.bosch.com>

Dave,

Samba-2.2.7a was released to fix 64bit file access issues. Strongly
suggest you update.

- John T.

On Thu, 19 Dec 2002, Windsor Dave (AdW/MOE2.1) wrote:
> Hello All,
>
> I recently upgraded one of my HP-UX servers from Samba 2.2.4 to 2.2.7.
> Since that time, I have noticed that disk activity on the file system where
> the Samba var directory is kept seems to be higher than I would expect.  We
> have now begun to experience a problem with PC clients running National
> Instruments' LabView software, installed on a Samba share.  When any PC
> client tries to execute it, disk utilization goes to 100% according to
HP's
> Glance performance monitor, with nearly all activity being in the
> aforementioned file system containing the Samba var files and being caused
> by the smbd for the client running LabView.  Using Glance to look at open
> files, I found that the only open file located in the Samba var file system
> is the smbd log file, and it is filled with messages like this:
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(660)
>
>   posix_fcntl_lock: WARNING: lock request at offset 0, length
> 9223372036854779000 returned
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(662)
>
>   an Invalid argument error. This can happen when using 64 bit lock offsets
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(663)
>
>   on 32 bit NFS mounted file systems.
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(677)
>
>   Count greater than 31 bits - retrying with 31 bit truncated length.
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(660)
>
>   posix_fcntl_lock: WARNING: lock request at offset 0, length
> 9223372036854779000 returned
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(662)
>
>   an Invalid argument error. This can happen when using 64 bit lock offsets
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(663)
>
>   on 32 bit NFS mounted file systems.
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(677)
>
> over and over again.  I have log level set to 1, with a different log for
> each client.  After several minutes, LabView finally loads and things
settle
> back down.  Any ideas as to what is happening?  The log mentions NFS, but
> the directories containing LabView are local to my system and are exported
> by Samba only, not NFS.
>
> My copy of Samba was compiled here using HP's ANSI C compiler under
HP-UX
> 11.11.  I ran configure with very few options, just to set the prefix and
to
> set "--with-utmp".  None of these problems occurred under Samba
2.2.4, and I
> haven't yet had a chance to try out 2.2.7a to see if there's any
difference.
> The problem occurs when running LabView with both NT4 and W2K clients. 
With
> our holiday shutdown almost here, I hope to get a chance to try 2.2.7a
> sometime tomorrow.
>
> Thanks in advance for any assistance!
>
> Dave Windsor
> AdW/MOE2.12
> Team Leader, Test Systems Engineering
> Robert Bosch Corporation
> Anderson, SC, USA
> email: <mailto:Dave.Windsor@us.bosch.com>
>
>
>
-- 
John H Terpstra
Email: jht@samba.org

Hmmmm....that sounds reasonable.  I have 2.2.7a compiled up and ready to
install as soon as our production test equipment shuts down, hopefully
tomorrow.  I'll post my results as soon as I get the chance.

Thanks!

Dave Windsor 
email: <mailto:Dave.Windsor@us.bosch.com> 

-----Original Message-----
From: John H Terpstra [mailto:jht@samba.org]
Sent: Thursday, December 19, 2002 6:24 PM
To: Windsor Dave (AdW/MOE2.1)
Cc: 'samba@lists.samba.org'
Subject: Re: [Samba] Strange locking errors with LabView under Samba
2.2.7 and HP-UX 1 1.11


Dave,

Samba-2.2.7a was released to fix 64bit file access issues. Strongly
suggest you update.

- John T.

On Thu, 19 Dec 2002, Windsor Dave (AdW/MOE2.1) wrote:
> Hello All,
>
> I recently upgraded one of my HP-UX servers from Samba 2.2.4 to 2.2.7.
> Since that time, I have noticed that disk activity on the file system
where
> the Samba var directory is kept seems to be higher than I would expect.
We
> have now begun to experience a problem with PC clients running National
> Instruments' LabView software, installed on a Samba share.  When any PC
> client tries to execute it, disk utilization goes to 100% according to
HP's
> Glance performance monitor, with nearly all activity being in the
> aforementioned file system containing the Samba var files and being caused
> by the smbd for the client running LabView.  Using Glance to look at open
> files, I found that the only open file located in the Samba var file
system
> is the smbd log file, and it is filled with messages like this:
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(660)
>
>   posix_fcntl_lock: WARNING: lock request at offset 0, length
> 9223372036854779000 returned
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(662)
>
>   an Invalid argument error. This can happen when using 64 bit lock
offsets
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(663)
>
>   on 32 bit NFS mounted file systems.
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(677)
>
>   Count greater than 31 bits - retrying with 31 bit truncated length.
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(660)
>
>   posix_fcntl_lock: WARNING: lock request at offset 0, length
> 9223372036854779000 returned
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(662)
>
>   an Invalid argument error. This can happen when using 64 bit lock
offsets
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(663)
>
>   on 32 bit NFS mounted file systems.
>
> [2002/12/19 17:47:17, 0] locking/posix.c:(677)
>
> over and over again.  I have log level set to 1, with a different log for
> each client.  After several minutes, LabView finally loads and things
settle
> back down.  Any ideas as to what is happening?  The log mentions NFS, but
> the directories containing LabView are local to my system and are exported
> by Samba only, not NFS.
>
> My copy of Samba was compiled here using HP's ANSI C compiler under
HP-UX
> 11.11.  I ran configure with very few options, just to set the prefix and
to
> set "--with-utmp".  None of these problems occurred under Samba
2.2.4, and
I
> haven't yet had a chance to try out 2.2.7a to see if there's any
difference.
> The problem occurs when running LabView with both NT4 and W2K clients.
With
> our holiday shutdown almost here, I hope to get a chance to try 2.2.7a
> sometime tomorrow.
>
> Thanks in advance for any assistance!
>
> Dave Windsor
> AdW/MOE2.12
> Team Leader, Test Systems Engineering
> Robert Bosch Corporation
> Anderson, SC, USA
> email: <mailto:Dave.Windsor@us.bosch.com>
>
>
>
-- 
John H Terpstra
Email: jht@samba.org