search for: brlock

[2799/3801] Compiling source3/locking/locking.c [2800/3801] Compiling source3/locking/brlock.c ../source3/locking/brlock.c: In function 'brl_get_locks_readonly_parser': ../source3/locking/brlock.c:2071: error: expected expression before 'struct' ../source3/locking/brlock.c:2071: warning: assignment makes pointer from integer without a cast ../source3/locking/brlock.c: In fu...

...r/cache/samba - Upgraded to 2.2.3 and 2.2.4 with the same error. - Added various debug levels within smb.conf to get information on why this is failing - all without success I finally got some information by running "strace smbstatus". This told me it couldn't find /var/cache/samba/brlock.tdb and /var/cache/samba/locking.tdb. Bizarrely, these files don't seem to be created *ever*, regardless of which version I use. I got rid of the error messages by performing the most awful hack. cp /var/cache/samba/messages.tdb /var/cache/samba/brlock.tdb cp /var/cache/samba/messages.tdb /va...

When using Samba 3.0.23b (slightly old, I know) on CentOS 4.4, smbstatus -B fails with a segmentation fault. smbstatus works, and tdbdump is able to dump brlock.tdb and locking.tdb without any errors (which is not what I expected). Here's the backtrace (non-ASCII characters replaced with 'X'): #0 0x0017fa2c in memcpy () from /lib/tls/libc.so.6 #1 0x0029b19f in tdb_write (tdb=0x89b8608, off=3083693360, buf=0x89b8608, len=144) at tdb/tdb.c...

...a smb.conf up. Just some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)): tdb_open_ex: could not open file /var/cache/samba/brlock.tdb: No such file or directory Failed to open byte range locking database tdb((null)): tdb_open_ex: could not open file /var/cache/samba/locking.tdb: No such file or directory ERROR: Failed to initialise locking database Can't initialise locking module - exiting i checked if a file locking.tdb...

I'm running 2.11, and I've noticed a number of log entries that look like so: angie.log: tdb(/usr/local/samba/var/locks/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) [2004/10/03 15:14:36, 0] tdb/tdbutil.c:tdb_log(531) tdb(/usr/local/samba/var/locks/brlock.tdb): expand_file ftruncate to 8192 failed (Permission denied) The files in question look like this: -rw-r--r-- 1 root root 8192 Oct 3 15:30 brlock.tdb -rw-r--r-- 1 root root 8192 Oct 3 11:30 locking.tdb Anything to be gained - or lost - by chmoding 666 on these...

...causes them to reboot, and the cluster did not come back up consistently. We eventually got it more or less stable with two nodes out of the 3, but we're still seeing worrying messages, eg we've just noticed: 2017/04/19 12:10:31.168891 [ 5417]: Vacuuming child process timed out for db brlock.tdb 2017/04/19 12:11:39.250169 [ 5417]: Unable to get RECORD lock on database brlock.tdb for 500 seconds ===== Start of debug locks PID=9372 ===== 8084 /usr/sbin/smbd brlock.tdb.2 7044 7044 20931 /usr/libexec/ctdb/ctdb_lock_helper brlock.tdb.2 7044 7044 W 21665 /usr/sbin/smbd brlock.tdb.2 174200 1...

...t; > > >Volker > > Any arguments that I can pass on would be much appreciated. The main argument is that Windows applications tend to coordinate access to files via byte-range locks. They expect data coherency under those byte range locks, meaning that if a value is written under a brlock, the brlock is released, and another process reads the value under the brlock, the value written must be visible. If this is not guaranteed, then data corruption will likely happen. The main question to the MooseFS developers would be under which circumstances a value written via pwrite on node A i...

...cks/printing.tdb): tdb_lock failed on list 80 ltype=2 (No record locks available) [2004/06/29 11:15:27, 0] printing/printing.c:(388) print_queue_update: Failed to lock printing database Other errors on file access [2004/06/29 11:00:45, 0] tdb/tdbutil.c:(531) tdb(/usr/lib/samba/var/locks/brlock.tdb): tdb_unlock: count is 0 [2004/06/29 11:00:45, 2] smbd/close.c:(229) janette closed file templat2/INVESTOR.BMP (numopen=7) [2004/06/29 11:00:45, 0] tdb/tdbutil.c:(531) tdb(/usr/lib/samba/var/locks/locking.tdb): tdb_lock failed on list 39 ltype=2 (No record locks available) [2004/06/29 11:0...

...ack to the previous release, which worked fine - only the acl stuff will not work perfect.) Thanks for your help! Bye, Peer p.s. Please send answers also directly to me. [2002/08/12 13:25:09, 0] tdb/tdbutil.c:(475) tdb((NULL)): tdb_open_ex: failed to get global lock on /var/opt/samba/locks/brlock.tdb: No locks available [2002/08/12 13:25:09, 0] locking/brlock.c:(233) Failed to open byte range locking database [2002/08/12 13:25:09, 0] tdb/tdbutil.c:(475) tdb((NULL)): tdb_open_ex: failed to get global lock on /var/opt/samba/locks/locking.tdb: No locks available [2002/08/12 13:25:09, 0] l...

I have successfully implemented Samba in the past but I am now perplexed by a new installation which fails smbstatus with the message: "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/brlock.tdb: No such file or directory Failed to open byte range locking database "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/locking.tdb: No such file or directory ERROR: Failed to initialise locking database Can't initialise module exiting" The files brlock.tdb and lock...

...some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)): tdb_open_ex: could not open file /var/cache/samba/brlock.tdb: No such file or directory Failed to open byte range locking database tdb((null)): tdb_open_ex: could not open file /var/cache/samba/locking.tdb: No such file or directory ERROR: Failed to initialise locking database Can't initialise locking module - exiting i checked if a file locking.tdb...

...ing...) 25067: typ=F_WRLCK whence=SEEK_SET start=32412 len=1 sys=4245464 pid=0 What's FD 10 you ask? # pfiles -F 25067 10: S_IFREG mode:0644 dev:85,60 ino:4630 uid:0 gid:0 size:327680 O_RDWR|O_LARGEFILE advisory read lock set by process 21130 /var/samba/locks/brlock.tdb At this point, cued by another post on this list, I tried a tdbdump on /var/samba/locks/brlock.tdb. It completed without issue however. pstack output: # pstack -F 25067 25067: /usr/sfw/sbin/smbd -D ff049c64 fcntl (a, 23, ffbff6f8) ff0398c0 fcntl (a, 23, ffbff6f8, 7e9c, fee02a00, 18...

Hi, I see samba with ctdb locking has following mapping when kernel oplocks = yes. share mode reservations = flock(2) posix byte range locking = fcntl(2) SMB locks (mandatory) = ctdb using brlock.tdb oplocks = fcntl(2) using F_SETLEASE Am I correct or I am missing something? I hope only SMB range locks are implemented with tdb, all else are being used from filesystem. What happens if flock or fcntl returns -ENOTSUPP, will samba start using other tdb files (locking.tdb) for that or wil...

In /varcache/samba/ I have several .tdb files. Like brlock.tdb, locking.tdb, ntdrivers.tdb, etc. Excusing my ignorance, what are these files, and what do they do? And why must they be copied when migrating from one samba server to a new one?

...x521b7544 name:smbXsrv_version_global.tdb path:/var/lib/ctdb/smbXsrv_version_global.tdb.1 dbid:0x6b06a26d name:smbXsrv_session_global.tdb path:/var/lib/ctdb/smbXsrv_session_global.tdb.1 dbid:0x68c12c2c name:smbXsrv_tcon_global.tdb path:/var/lib/ctdb/smbXsrv_tcon_global.tdb.1 dbid:0x4e66c2b2 name:brlock.tdb path:/var/lib/ctdb/brlock.tdb.1 dbid:0x7a19d84d name:locking.tdb path:/var/lib/ctdb/locking.tdb.1 dbid:0x06916e77 name:leases.tdb path:/var/lib/ctdb/leases.tdb.1 dbid:0x66f71b8c name:smbXsrv_open_global.tdb path:/var/lib/ctdb/smbXsrv_open_global.tdb.1 dbid:0x5bcfcbd7 name:printer_list.tdb path...

...(183) change_to_user: Skipping user change - already user [2008/11/19 11:32:28, 10] locking/brlock.c:brl_get_locks_internal(1648) brl_get_locks_internal: 0 current locks on dev=64783, inode=612495337 [2008/11/19 11:32:28, 10...

...> Volker >> Any arguments that I can pass on would be much appreciated. > The main argument is that Windows applications tend to coordinate access > to files via byte-range locks. They expect data coherency under those > byte range locks, meaning that if a value is written under a brlock, > the brlock is released, and another process reads the value under the > brlock, the value written must be visible. If this is not guaranteed, > then data corruption will likely happen. The main question to the > MooseFS developers would be under which circumstances a value written &g...

On Sat, Apr 22, 2006 at 06:15:31PM +0100, Daniel J Blueman wrote: > As a test, I changed the opening of the locking.tdb and brlock.tdb > files to use the TDB_INTERNAL flag, avoiding use of the fcntl(F_SETLK) > syscall for locking individual database records. Performance was a lot > snappier, with quite a bit less system time used. > > What is the scope of implementing shared memory TDBs, where locking > coul...

Hi list We recently upgraded our fileservers from Centos supplied 4.2.10 to Sernet 4.4.6, and then our DCs from 3.6.x to 4.4.6. It seems that since then we've had problems with locks not being obeyed on all nodes - they only seem to work when a second client opens a file on the same node as the first client. For example, when a user opens an Excel file I will see something like this

Hello, maybe there is someone they can help and answer a question why i get these network screen on my ctdb clusters. I have two ctdb clusters. One physical and one in a vmware enviroment. So when i transfer any files (copy) in a samba share so i get such network curves with performance breaks. I dont see that the transfer will stop but why is that so? can i change anything or does anybody know