search for: posix_fcntl_lock

...following line in fstab: <IP-Number>:/vgroup00/data02/data /mnt/nas01 nfs rsize=8192,wsize=8192,soft 0 0 I tried to save a file from word which lead to a aprox. 1 minute hang of my Win2k/SP3. The log of the machine showed following lines: [2003/11/11 10:20:36, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 2147483539, length 1 returned [2003/11/11 10:20:36, 0] locking/posix.c:posix_fcntl_lock(658) an No locks available error. This can happen when using 64 bit lock offsets [2003/11/11 10:20:36, 0] locking/posix.c:posix_fcntl_lock(659) o...

...he AFS partion is already mounted before I login to Samba from the win2k machine so Samba should just see the files there. I started nmbd and smbd with the -d 1 option and the log.%m file for the win2k machine is very big but essentially full of things like: [2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(660) posix_fcntl_lock: WARNING: lock request at offset 2147483539, length 1 returned [2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(662) an Invalid argument error. This can happen when using 64 bit lock offsets [2002/09/21 00:01:25, 0] locking/posix.c:posix_fcntl_lock(663) on 32 bi...

...s, Chris Haidinyak SAMBA LOG TRANSCRIPT SNIPPET ---------------------------- [2004/02/16 10:03:52, 0] smbd/server.c:main(791) smbd version 2.2.8a-SuSE started. Copyright Andrew Tridgell and the Samba Team 1992-2002 tron:/var/log/samba # tail log.smbd [2004/02/16 10:06:02, 0] locking/posix.c:posix_fcntl_lock(658) an No locks available error. This can happen when using 64 bit lock offsets [2004/02/16 10:06:02, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file systems. [2004/02/16 10:06:02, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset...

...I am getting the following error messages, which go away if I set posix locks = no, but the corruption doesn't go away. I'm not using NFS at all, and the drive is local. In fact, NFS is not even compiled in this kernel. I'm on a 32-bit system. 2004/06/02 00:41:53, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 0, length 92233720368547758\ 08 returned [2004/06/02 00:41:53, 0] locking/posix.c:posix_fcntl_lock(658) an Invalid argument error. This can happen when using 64 bit lock offsets [2004/06/02 00:41:53, 0] locking/posix.c:posix_fcntl_lock(659...

...word 2003 sp1 (and same from word 2000) it tells me: on the win98se and win xp pro sp2 clients: "Microsoft Office Word" Word cannot complete the save due to a file permission error. (I:\transfer\ursr\chidren\2005.doc) and on the server it logs [2005/04/11 11:03:06, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file systems. [2005/04/11 11:03:07, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2005/04/11 11:03:07, 0] locking/posix.c:posix_fcntl_lock(658) an No locks available error. This can happ...

....5. The windows homedirs are on \\server\username, the UNIX homedirs are NFS mounted by the server. So, whenever I access \\server\username this actually NFS-mounts /nfs/client/home/username. I now have one client machine that causes the following error: [2001/11/05 19:17:56, 0] locking/posix.c:posix_fcntl_lock(669) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2001/11/05 19:17:56, 0] locking/posix.c:posix_fcntl_lock(670) an No locks available error. This can happen when using 64 bit lock offsets [2001/11/05 19:17:56, 0] locking/posix.c:posix_fcntl_lock(671) on 32...

...ver 1200 with gentoo linux and kernel 2.6.9-ac12 i've simply exported my smbroot (on alpha, it is my fileserver) and have samba running on an intel pentium4 box, also gentoo, kernel 2.6.0-ac12. Seems to work, eccept some locking problems. smbd[9450]: [2005/02/08 17:29:51, 0] locking/posix.c:posix_fcntl_lock(657) smbd[9450]: posix_fcntl_lock: WARNING: lock request at offset 0, length 1 returned smbd[9450]: [2005/02/08 17:29:51, 0] locking/posix.c:posix_fcntl_lock(658) smbd[9450]: an No locks available error. This can happen when using 64 bit lock offsets smbd[9450]: [2005/02/08 17:29:51, 0] locki...

...dows machine to my samba share. It told me "There is not enough disk space". However, it lets me copy it in another share. I didn't notice anything different with the share I am having problem with. I noticed the following messages in the log: [2005/08/10 13:56:47, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 34836480, length 61440 returned [2005/08/10 13:56:47, 0] locking/posix.c:posix_fcntl_lock(658) an Invalid argument error. This can happen when using 64 bit lock offsets [2005/08/10 13:56:47, 0] locking/posix.c:posix_fcntl_lock(659) on 32...

We're seeing problems with copying files > 2BG to a samba share. Google says that, as of 2004, there was a 2GB file size limit in that scenario, but I haven't found anything more recent. Is that still the case or am I looking at a different problem? Thanks, Graham

...orting an NFS mounted share on a NetAPP fileserver connected to eth1 via samba out eth0. All PCs are able to write fine but when writing to the share via a mac using OSX the MAC errored out with permission denied and the samba logs showed the following [2004/02/09 16:48:01, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 0, length 4294967295 returned [2004/02/09 16:48:01, 0] locking/posix.c:posix_fcntl_lock(658) an No locks available error. This can happen when using 64 bit lock offsets [2004/02/09 16:48:01, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit...

When an XP box is reading a file from the Samba server performance is what you would expect with 100 mbs ethernet. When uploading a large file (>1 meg) performance is very slow. 1/20th what I would expect. The Samba server log has these entries: posix_fcntl_lock: WARNING: lock request at offset 12226560, length 61440 returned [2004/12/24 17:28:52, 0] locking/posix.c:posix_fcntl_lock(658) an Invalid argument error. This can happen when using 64 bit lock offsets [2004/12/24 17:28:52, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file sys...

...e below): [2004/01/22 16:31:13, 3] lib/util.c:fcntl_lock(1632) fcntl_lock: fcntl lock gave errno 37 (No locks available) [2004/01/22 16:31:13, 3] lib/util.c:fcntl_lock(1650) fcntl_lock: lock failed at offset 687 count 1 op 13 type 0 (No locks available ) [2004/01/22 16:31:13, 0] locking/posix.c:posix_fcntl_lock(656) posix_fcntl_lock: WARNING: lock request at offset 687, length 1 returned [2004/01/22 16:31:13, 0] locking/posix.c:posix_fcntl_lock(658) an No locks available error. This can happen when using 64 bit lock offsets [2004/01/22 16:31:13, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After 2GB of transfer, files stop being written by Samba. I keep getting Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37, 0] locking/posix.c:posix_fcntl_lock(656) Jun 12 11:29:37 nasserver smbd[8715]: posix_fcntl_lock: WARNING: lock request at offset 558761983, length 1 returned Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37, 0] locking/posix.c:posix_fcntl_lock(658) Jun 12 11:29:37 nasserver smbd[8715]: an Invalid argument error. This ca...

...t their MS Office files over our Samba shares (Samba 3.0.10, CentOS4 w/ their i386 RPM). It looks like the clients' attempts to lock the files fails. When their client attempts to open such a file, Samba reports: ----------8<----------------------- [2006/10/27 15:55:57, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2006/10/27 15:55:57, 0] locking/posix.c:posix_fcntl_lock(658) an No locks available error. This can happen when using 64 bit lock offsets [2006/10/27 15:55:57, 0] locking/posix.c:posix_fcntl_lock(659) on 32...

...ry(392) add_posix_lock: File mp3/bar/dilbert030923.gif: type = WRITE: start=0 size=4294967295: dev=833 inode=19598 [2004/02/12 00:07:40, 5] locking/posix.c:set_posix_lock(1055) set_posix_lock: Real lock: Type = WRITE: offset = 0, count = 4294967295 [2004/02/12 00:07:40, 8] locking/posix.c:posix_fcntl_lock(650) posix_fcntl_lock 22 13 0 4294967295 1 [2004/02/12 00:07:40, 8] lib/util.c:fcntl_lock(1308) fcntl_lock 22 13 0 4294967295 1 [2004/02/12 00:07:40, 3] lib/util.c:fcntl_lock(1319) fcntl_lock: fcntl lock gave errno 75 (Value too large for defined data type) [2004/02/12 00:07:40, 3] lib/util.c...

...[2004/08/27 18:29:01, 10] locking/posix.c:is_posix_locked(697) is_posix_locked: File wk/xx, offset = 0, count = 16384, type = READ [2004/08/27 18:29:01, 10] locking/posix.c:posix_lock_in_range(633) posix_lock_in_range: offset_out = 0, count_out = 16384 [2004/08/27 18:29:01, 8] locking/posix.c:posix_fcntl_lock(650) posix_fcntl_lock 25 5 0 16384 0 [2004/08/27 18:29:01, 8] lib/util.c:fcntl_lock(1646) fcntl_lock 25 5 0 16384 0 [2004/08/27 18:29:01, 8] locking/posix.c:posix_fcntl_lock(680) posix_fcntl_lock: Lock call failed [2004/08/27 18:29:01, 10] locking/locking.c:is_locked(101) is_locked: pos...

We are receiving the following in our logs: Mar 18 13:41:37 athena smbd[24222]: [2005/03/18 13:41:37, 0] locking/posix.c:posix_fcntl_lock(658) Mar 18 13:41:37 athena smbd[24222]: an Invalid argument error. This can happen when using 64 bit lock offsets Mar 18 13:41:37 athena smbd[24222]: [2005/03/18 13:41:37, 0] locking/posix.c:posix_fcntl_lock(659) Mar 18 13:41:37 athena smbd[24222]: on 32 bit NFS mounted file systems. Mar 18 13...

Hi, Here's my problem: Samba-2.2.x (even 2.2.7) compiled right out of the box on HP/UX 11.00 gives some errors in the log file: Nov 23 16:17:32 pandora smbd[6744]: [2002/11/23 16:17:32, 0] locking/posix.c:posix_fcntl_lock(661) Nov 23 16:17:32 pandora smbd[6744]: posix_fcntl_lock: WARNING: lock request at offset 0, length 9223372036854779000 returned Nov 23 16:17:32 pandora smbd[6744]: [2002/11/23 16:17:32, 0] locking/posix.c:posix_fcntl_lock(662) Nov 23 16:17:32 pandora smbd[6744]: an Invalid argument error. T...

...to Samba, and on Solaris it is on by default. The value of tcp_keepalive_interval is 7200000. I can change this value, but don't want to mess with it unless I'm really sure of what I'm doing. Why the invalid argument error? Next one is this: [2004/01/10 00:06:12, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 0, length 922337203685477900 0 returned [2004/01/10 00:06:12, 0] locking/posix.c:posix_fcntl_lock(658) an Invalid argument error. This can happen when using 64 bit lock offsets [2004/01/10 00:06:12, 0] locking/posix.c:posix_fcntl_lock(659...

...le cfenton/Butzlaff/Wettbewerb Stifterverband/Marketing.doc: type = READ: start=2147483560 size=1: dev=65024 inode=36110346 [2004/03/02 15:03:56, 5] locking/posix.c:set_posix_lock(1054) set_posix_lock: Real lock: Type = READ: offset = 2147483560, count = 1 [2004/03/02 15:03:56, 8] locking/posix.c:posix_fcntl_lock(650) posix_fcntl_lock 25 13 2147483560 1 0 [2004/03/02 15:03:56, 8] lib/util.c:fcntl_lock(1621) fcntl_lock 25 13 2147483560 1 0 [2004/03/02 15:03:56, 8] lib/util.c:fcntl_lock(1656) fcntl_lock: Lock call successful [2004/03/02 15:03:56, 8] locking/posix.c:posix_fcntl_lock(680) posix_fcntl_lo...