search for: brlocking

[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 function

Hi! I've been fighting with Samba for over a week now and I can't seem to work it out. It all started when I installed the standard samba (2.2.1a-4) which came with RH7.2. I ran "smbstatus" and got the following error: Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting. I've tried the

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

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made 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

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:

Hi, This morning our CTDB managed cluster took a nosedive. We had member machines with hung smbd tasks which 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

On Thu, Jul 14, 2016 at 02:39:48PM +0100, Alex Crow wrote: > >The main hint I would like to give to the MooseFS developers is to get > >ping_pong -rw working. If you need any assistance in setting that up > >and getting arguments on why this is important, let us know! > > > >With best regards, > > > >Volker > > Any arguments that I can pass on would

We've just gone live with a file & print server, and are having major problems with Samba. When used out of hours, with all PCs switched on and connected to the domain, everything works fine. However, during the day, we have problems where users can't print to any samba-hosted printer, Access database applications (where the database is held on the server) won't work, or work

Hi, we have installed the newest release of samba from HP for HPUX. It's based on samba 2.2.3a (B8725-1.0.8 HP number) We used the same config file and started the samba stuff and run into the following problems. 1) The machine was only reachable under one netbios alias. 2) Only some pc could connect (~15 out of 150), but those could also only see the toplevel of a share 3) The following

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:

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made 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)):

(Yes, I should upgrade Samba to 3.0.35). We're running the Sun provided Samba daemon (SUNWsmbau and friends) on Solaris 10 Generic_138888-08 (sparc). Lots of Windows clients (mixed XP, 2003, 2008) hit this server and periodically we'll start seeing smbd processes begin piling up. These processes can't be killed with a normal kill -- only kill -9 will do the trick. In the past

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

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?

On 20/10/16 14:10, Amitay Isaacs wrote: > On Thu, Oct 20, 2016 at 8:09 PM, Alex Crow via samba > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > 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

Hello! Recently I moved some file shares from old server to new one with CentOS 5.2 and samba 3.0.32. And yesterday we found that antivirus (nod32 ) installed on users computers do strange thing- it's often locks and locks files. Here is part of log with debug level = 10 [2008/11/19 11:32:28, 3] smbd/process.c:switch_message(927)

On 14/07/16 14:51, Volker Lendecke wrote: > On Thu, Jul 14, 2016 at 02:39:48PM +0100, Alex Crow wrote: >>> The main hint I would like to give to the MooseFS developers is to get >>> ping_pong -rw working. If you need any assistance in setting that up >>> and getting arguments on why this is important, let us know! >>> >>> With best regards,

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

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