similar to: Performance Question: Lots of Small Files vs One Large File

Is this a protocol issue? A decade ago I saw writes to small files less than 16k were awful, because the cost of opening and other file ops dwarfed writing actual content. So very small files should be slow, but these files are 10mb each. Or is this a Windows issue? If so, what's causing the problem? Just trying to understand. On Tue, Oct 6, 2020 at 2:39 PM Ralph Boehme <slow at

Hi Martin It seems as though, when I go from `clustering = no` to `clustering = yes`, if I do a domain join, it will fail. However, if I do a `systemctl restart ctdb` (knowing full well it will fail every time), if after this I add a sleep(15), then do a domain join, then do a `systemctl restart ctdb`, then the join will have worked, AND CTDB will start properly. So in a nutshell, in Ansible, -

How can setlmasterrole be set persistently? Is there a way to put it in some config file? If not, if setting it from the command line is the only option, what is the recommended approach to ensure it is set upon reboot? Thx -- BOB BUCK SENIOR PLATFORM SOFTWARE ENGINEER SKIDMORE, OWINGS & MERRILL 7 WORLD TRADE CENTER 250 GREENWICH STREET NEW YORK, NY 10007 T (212) 298-9624 ROBERT.BUCK at

Martin, Here you go, # echo "mypassword" | net --no-dns-updates -U service-account-name ads testjoin domain.local kerberos_kinit_password NETBIOS_NAME$@DOMAIN.LOCAL failed: Client not found in Kerberos database Join to domain is not valid: The name provided is not a properly formed account name. On Wed, Sep 30, 2020 at 9:34 PM Martin Schwenke <martin at meltin.net> wrote:

On Thu, Oct 15, 2020 at 09:01:01AM -0400, Robert Buck via samba wrote: > Can someone please respond to this question? We're unsure how to > persistently set these flags, which are VERY useful for performance from > what we see. We want to ensure that after reboot, particular nodes are > always set on (or others off). From the ctdb/doc/ctdb.1.xml man page file:

Hi Team, I'm working on a CTDB Prometheus Exporter. I have two questions... First, does anyone have an "internal" cheat sheet on the metrics and their descriptions? I didn't really see much online, or in the source code. Thanks -- BOB BUCK SENIOR PLATFORM SOFTWARE ENGINEER SKIDMORE, OWINGS & MERRILL 7 WORLD TRADE CENTER 250 GREENWICH STREET NEW YORK, NY 10007 T (212)

Running into problems configuring different locations for the volatile and other database directories. Can someone provide a quick sanity check on what I'm doing below? Thank you. Given [database] volatile database directory = /var/cache/dbdir/volatile persistent database directory = /var/cache/dbdir/persistent state database directory = /var/cache/dbdir/state And given, [root

Quick question... The docs for vfs readahead mention Windows Vista, but what about modern Windows versions? Windows Server 2016 or Windows Server 2019? Thank you, -- BOB BUCK SENIOR PLATFORM SOFTWARE ENGINEER SKIDMORE, OWINGS & MERRILL 7 WORLD TRADE CENTER 250 GREENWICH STREET NEW YORK, NY 10007 T (212) 298-9624 ROBERT.BUCK at SOM.COM

Thanks, I'll do that. It might be a week or two. But I have solid C skills going back 25 years, and spent a decade doing C++. Let me know if there's a "getting started guide" for developers on the Samba project. Key tools to install, etc. I will need to spin up a VM to work in. Also, should chat with the CTO so he's aware. On Thu, Nov 12, 2020 at 4:46 AM Martin Schwenke

Hi Folks, We're in the process of setting up a Samba cluster (Samba+CTDB+etcd), and we (presently) using Winbind. We use AD. We're finding that the domain join (or kerberos ticket renewal) is unreliable. Every day we find Samba/Winbind is no longer joined to the domain. Now, we're in a bit of a learning curve here, and automating everything with Terraform + Ansible. We have yet to

Folks, thank you for being so helpful. I can't quite figure out the exact command line to get ctdb dbstatistics for the locking.tdb in CSV format. How do you do this? [root at use1-samba-server-c25-use1-01 ec2-user]# ctdb -X --separator=, dbstatistics locking.tdb --help Usage: [OPTION...] -d, --debug=STRING debug level -t, --timelimit=INT timelimit (in seconds) -n,

Superb. I'll take a look. Thank you On Tue, Oct 6, 2020 at 1:46 AM Martin Schwenke <martin at meltin.net> wrote: > Hi Bob, > > On Mon, 5 Oct 2020 09:31:59 -0400, Robert Buck <robert.buck at som.com> > wrote: > > > It seems as though, when I go from `clustering = no` to `clustering = > yes`, > > if I do a domain join, it will fail. However, if I do a

What is the impact of turning profiling on? profiling support = on More specifically, we're setting up a custom Prometheus exporter for Samba, but smbstatus does not provide a whole lot of detailed information for samba health, etc. I was hoping for more detailed information that we can forward to Prometheus. So my question is: 1. What options exist for efficiently getting metrics?

Hi I have a question regarding CTDB RecLockLatencyMs tunable parameter. Is there any relationship between the RecLockLatencyMs property and the RecoverInterval property? Does one need to be larger than the other? Or if RecLockLatencyMs were increased to 5000ms, should some other setting be changed in proportion? We're using a geo-distributed etcd cluster for the CTDB recovery lock and I

Am 10/6/20 um 7:49 PM schrieb Robert Buck via samba: > In an architecture where we have Samba running on RHEL exposing shares to > Windows, when we have 1 large 1GB file, the write performance to storage is > very fast, even over distances of 5000 miles. However, even writes to local > Samba servers, with 100 10MB files being copied onto a shared drive, > Windows Explorer is MUCH

Hi Jeremy, and Martin, Digging in the code I think I figured it out (though untested). Here is my Ansible fragment. Is this correct for the property names? ... [legacy] realtime scheduling = false {% if ctdb_lmaster_capability is defined %} lmaster capability = {{ ctdb_lmaster_capability }} {% endif %} {% if ctdb_recmaster_capability is defined %} recmaster capability = {{

Hi Jeremy, thank you for your very helpful response. We're looking at a few more options. Would you have the time to provide some guidance on these, how helpful they may be? - *aio ** -> https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#AIOREADSIZE - *write cache* -> https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#WRITECACHESIZE -

We've only seen this error once, just occurred. We were having domain join issues. Enter ******@*******.local's password: ../../source3/lib/dbwrap/dbwrap_ctdb.c:855 ERROR: new_seqnum[10] != old_seqnum[8] + (0 or 1) after failed TRANS3_COMMIT - this should not happen! secrets_store_JoinCtx: dbwrap_transaction_commit() failed for SOMDEV libnet_join_joindomain_store_secrets:

Ok, thanks. [root at euw2-samba-server-c21-01 ec2-user]# systemctl status winbind.service *?* winbind.service - Samba Winbind Daemon Loaded: loaded (/usr/lib/systemd/system/winbind.service; enabled; vendor preset: disabled) Active: *failed* (Result: exit-code) since Wed 2020-09-30 12:58:25 UTC; 1s ago Docs: man:winbindd(8) man:samba(7) man:smb.conf(5)

Hi Bob, On Thu, 15 Oct 2020 16:37:18 -0400, Robert Buck <robert.buck at som.com> wrote: > Digging in the code I think I figured it out (though untested). Here is my > Ansible fragment. Is this correct for the property names? > > ... > [legacy] > realtime scheduling = false > {% if ctdb_lmaster_capability is defined %} > lmaster capability = {{