search for: fcntl_getlock

...nds connection. ............................ [2018/10/23 09:27:35.529661,  3] ../source3/smbd/smb2_read.c:413(smb2_read_complete)   smbd_smb2_read: fnum 591422384, file Navidata/Common/Cash.mdb, length=16384 offset=85655552 read=16384 [2018/10/23 09:27:35.531806,  3] ../source3/lib/util.c:1183(fcntl_getlock)   fcntl_getlock: fd 45 is returned info 2 pid 0 [2018/10/23 09:27:35.531860,  3] ../source3/smbd/smb2_read.c:413(smb2_read_complete)   smbd_smb2_read: fnum 591422384, file Navidata/Common/Cash.mdb, length=16384 offset=85671936 read=16384 [2018/10/23 09:27:35.533803,  3] ../source3/lib/util.c:1...

...depends on the game). Here is what I believe to be a relevant chunk of the logs: > [2017/06/25 16:33:39.646102, 3] > ../source3/smbd/process.c:1538(switch_message) > switch message SMBreadX (pid 23003) conn 0x557ede2f1420 > [2017/06/25 16:33:39.646149, 3] ../source3/lib/util.c:1183(fcntl_getlock) > fcntl_getlock: fd 35 is returned info 2 pid 0 > [2017/06/25 16:33:39.646193, 3] > ../source3/smbd/reply.c:4178(send_file_readX) > send_file_readX fnum 62440 max=2048 nread=2048 > [2017/06/25 16:33:39.649153, 3] > ../source3/smbd/process.c:1957(process_smb) > Transact...

...73) posix_lock_in_range: offset_out = 330004, count_out = 24 [2008/11/19 11:32:28, 8] locking/posix.c:posix_fcntl_getlock(235) posix_fcntl_getlock 28 330004 24 0 [2008/11/19 11:32:28, 8] lib/util.c:fcntl_ge...

...program that is running very, very slow on version 3.6.8. Using SMB2, logging level 3 I saw a lot of these: [2012/09/24 23:44:43.824970, 3] smbd/smb2_read.c:356(smb2_read_complete) smbd_smb2_read: fnum=[8523/filename] length=2 offset=1656 read=2 [2012/09/24 23:44:43.825499, 3] lib/util.c:1498(fcntl_getlock) fcntl_getlock: fd 34 is returned info 2 pid 0 Seems the files are read in chunks of 2 bytes a call. Most of the files the program is reading are a few Mb, so why is it only reading 2 bytes at a time? In ver 3.6.7 I made a few tests also, and it does matter what you choose for locking, e.g.:...

..................... > > [2018/10/23 09:27:35.529661,  3] > ../source3/smbd/smb2_read.c:413(smb2_read_complete) >   smbd_smb2_read: fnum 591422384, file Navidata/Common/Cash.mdb, > length=16384 offset=85655552 read=16384 > [2018/10/23 09:27:35.531806,  3] ../source3/lib/util.c:1183(fcntl_getlock) >   fcntl_getlock: fd 45 is returned info 2 pid 0 > [2018/10/23 09:27:35.531860,  3] > ../source3/smbd/smb2_read.c:413(smb2_read_complete) >   smbd_smb2_read: fnum 591422384, file Navidata/Common/Cash.mdb, > length=16384 offset=85671936 read=16384 > [2018/10/23 09:27:35.533803, ...

...ing the activity in top shows that during these 30 seconds the smbd process for the client is consuming all processing power it can get (on one core). Having set "loglevel = 2 locking:10" the log gets filled up with entries like these: [2010/03/05 20:04:30, 8] locking/posix.c:234(posix_fcntl_getlock) posix_fcntl_getlock 105 4729736 242 0 [2010/03/05 20:04:30, 8] lib/util.c:1832(fcntl_getlock) fcntl_getlock fd=105 offset=4729736 count=242 type=0 [2010/03/05 20:04:30, 3] lib/util.c:1856(fcntl_getlock) fcntl_getlock: fd 105 is returned info 2 pid 0 [2010/03/05 20:04:30, 8] locking/posix....

Dear all, I have set up a two node workin gluster with glusterfs3.1 and Samba-Sernet 3.5. Everything is working great except MSOffice files (Word/Excell). On the gluster-vol they have the strange behavior That they rest read only, write protected. Every other type of files can be manged without problem, openoffice files too. So when I save a word file on the vol and try to change it it is write

Hi, I've noticed that over a WAN (T1) I'm getting incredibly slow file copy performance. Using smbclient on a linux machine on one size of the WAN, As you can imagine, this makes all of our file shares unusable over the WAN. It's not an issue with WAN performance, because using scp to transfer the same file, I get speeds of ~145k/s. A tcpdump of the file copy of ~2MB file that actually

...e opened file renate/My Documents/My Pictures/desktop.ini read=Yes write=No (numopen=4) [2015/12/19 22:47:00.848688, 2] ../source3/smbd/close.c:780(close_normal_file) ALPHA\bouke closed file bouke/Desktop/Opera.lnk (numopen=11) NT_STATUS_OK [2015/12/19 22:47:00.851135, 3] ../source3/lib/util.c:1181(fcntl_getlock) fcntl_getlock: fd 57 is returned info 2 pid 0 [2015/12/19 22:47:00.851176, 3] ../source3/smbd/smb2_read.c:413(smb2_read_complete) smbd_smb2_read: fnum 3879432779, file renate/My Documents/My Pictures/desktop.ini, length=520 offset=0 read=520 [2015/12/19 22:47:00.853536, 2] ../source3/smbd/open.c:1...

Are their issues with Samba and Lustre working together? I remember something about turning oplocks off in samba, and while testing samba I noticed this [2010/08/27 17:30:59, 3] lib/util.c:fcntl_getlock(2064) fcntl_getlock: lock request failed at offset 75694080 count 65536 type 1 (Function not implemented) But I also found out about the flock option for lustre. Should I set flock on all clients? or can I just use localflock option on the fileserver? David -- Personally, I liked the universi...

I am running two Fedora 13 servers, one as a Samba PDC and the other as a BDC. For the past week I have been tracing a series of issues which may or may not be related to Samba 3.5.4. Here is one problem that I am tracking and need help from the list with suggestions. >From a wireshark trace between my Samba server and an XP client I am seeing the following error status returned for up to a