similar to: brlock.tdb and locking.tdb always missing on RH 7.2

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

(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

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

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:

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

i have taken a default intel redhat 7.2 machine which came with samba 2.2.1a and removed samba, samba-common, samba-client and samba-swat. i also removed /etc/samba and /var/lock/samba and all samba log files i then installed the samba RPM for samba 2.2.5 from: http://se.samba.org/samba/ftp/Binary_Packages/redhat/RPMS/7.2/samba-2.2.5- 1.i386.rpm i then installed this with rpm -ivh

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?

[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 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)):

I am running debian sarge 2.4.27-3-686 and samba version 3.0.14a-Debian . The previous machine was running rh 7.3 (valhalla) 2.4.20-29.7.progeny.11, samba version unknown. I have restored all shares and directories. Most of users can access everything, however our login script will not run. For those users that cannot log in re-joining them to the domain not only works but then the login

Hi, Does someone know a document which explains the TDB structure. functionalites, and format of the TDB files etc. I need to understand why some of the TDBs like messages.tdb, unexpected.tdb, brlock if not read_only, locking.tdb, session.tdb, wins.tdb are called with TDB_CLEAR_IF_FIRST tdb flags. Why some TDBs are opend with O_RDWR|O_CREAT flags viz. gencache.tdb, group_mapping.tdb,

Hello, I have been tracking this bug as much as possible, and it appears there is a severe problem in the code that deals with .tdb files. Lately our samba 2.2 testbed has been having painfully slow network responsiveness. It would go 30-60 seconds without a response to a client on many occasions (both browsing the network, and opening files/refreshing directories). Clients include Windows 98se,

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

On Sat, Apr 22, 2006 at 06:15:31PM +0100, Daniel J Blueman wrote: > I did some smbd profiling, and was seeing quite a lot of time spent > (un)locking [1] TDB files. > > A quick workload of opening a few directory trees, we see a _lot_ of > activity with a few TDB files: > > locking.tdb: 11943 accesses > brlock.tdb: 690 accesses > group_mapping.tdb: 126 accesses >

Thanks very much, Volker. I want to synchronize three tdb files(listed as below) which is relevant to the opened file: 1) brlock.tdb 2) locking.tdb 3) smbXsrv_open_global.tdb These three tdb files are used to realize the durable file handle feature. As what you have said, the performance will be affected if storing these three files in the shared storage. So can I realize the synchronization

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

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

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