similar to: oplocks, kernel oplocks, kernel share modes, .. - how it all works?

On Tue, Jan 24, 2023 at 08:29:17PM +0300, Michael Tokarev via samba wrote: >24.01.2023 20:22, Ralph Boehme via samba wrote: >>What Samba version is this? This: >> >>>LEASE() >> >>... looks broken: the handle oplock/lease state claims to be a >>lease, which means the client didn't request an oplock but a lease >>which should not have happened in

On Wed, Jan 25, 2023 at 12:33:57AM +0300, Michael Tokarev wrote: >>@Michael: move the kernel oplocks setting to the global section, then things may start to work as expected. > >With kernel oplocks = yes in [global] but without mentioning >smb2 leases, this thing behaves in a way similar to when setting >smb2 leases to no (also globally, as it is a global parameter), -- >I see

24.01.2023 20:09, Jeremy Allison via samba wrote: > On Tue, Jan 24, 2023 at 12:38:29PM +0300, Michael Tokarev via samba wrote: >> >> Here we've two files open, with kernel oplocks = yes (hence it is LEASE(), - >> before I enabled kernel oplocks, it was LEASE(RH) or LEASE(RWH)). > > Kernel oplocks do not support SMB2+ LEASES. So you're > just seeing old

Hello, I am using the vfs_gpfs samba module to map ACLs through samba. It works fine on files, but directory ACLs are ignored. Ex: getfacl /sb/share/myplace/ file: sb/share/myplace/ owner: root group: root user::rwx user:afrankel:rwx group::--- mask::rwx other::--- When I try to access this folder in Windows, I get permission denied. The same permissions on a files, I can open it / modify it

Hi, I'm trying to set up samba share exporting gpfs filesystem and I strugle with setting sharemode to yes. Samba is 3.6.5, gpfs version is 3.2.1-29 (the latest available for 3.2 branch). Everything works fine when sharemode is set to no, but I'd rather insist to switch it to yes. That's what man page says: no - do not propagate sharemodes across all GPFS nodes. This should only be

Hello Volker, I was able to get those level 10 logs - spitted by machine. Unfortunately I don't know how attachments behave - Groupwise seems not to be happy with those - so I try the redundant way: Here are the logfiles for this event (only one machine, one try): https://www.bitmammut.de/WDR/log.klnmszap32 In this file there are about 3 occurrences of the

On 30/06/2020 14:55, Ralph Boehme via samba wrote: > Howdy! > > Am 6/30/20 um 2:37 PM schrieb Georg.Biberger--- via samba: >> We are using Samba 4.10.16 as a readonly file server on a linux box with SLES 12. All is working fine with our NAS NFS Shares. We are now trying to integrate new NFS Shares from an archive provider. We have some problems with samba not responding, when

Hello all, As a Samba programming newbie, I've run onto a question that doesn't have an obvious answer in FAQ or googled literature. I need to lock large numbers of files on the server, and have Samba open requests block until they are released. I found references to "blocking locks" in references such as "Using Samba" (O'Reilly, 1999, 2003)

Hi all, At some point recently my customers can no longer see GPFS snapshots under the Windows Previous Versions tab. It simply says "No previous versions available". If a fileset is exported with the flag "force user = root" then Previous Versions *are* displayed. [2016/07/06 10:07:35.602080, 3] ../source3/smbd/vfs.c:1322(check_reduced_name) check_reduced_name:

Hi Can anyone advise me on "kernel oplocks" in a ctdb cluster. I have a ctdb (GPFS is the parallel file system) setup that uses samba (3.5.8) for cifs and IBM CNFS for NFS. Reading the documentation on kernel oplocks it seems to me that I can export the same area via samba and NFS with "kernel oplocks = Yes" . My logic is that IBM CNFS has shared NFS locking

I have been working on a CTDB cluster on and off for a while now. I had it working great for a while. THen I decide dthat I wanted to change the configuration of my replicated volumes. I changed my DRBD configuration to match my desired configuration. Now I can get the CTDB to work quite right. I am able to join the cluster to the domain without issues. I can also list my ad users and groups using

Also from my observation, based on network packets and time measurements, it seems the CIFS clients haven't done any sort of cache. For example, doing a "ls" for 5 times on the same folder within a short period of time. The network packet sizes are almost equal every time and the time it takes is similar. Isn't there supposed to be some page cache or dentry cache that could

Hi All, I am running Samba version 3.0.7-2.FC2. I've been noticing the following messages in /var/log/messages: Sep 22 09:35:47 www kernel: lease broken - owner pid = 6024 Sep 22 09:36:32 www kernel: lease broken - owner pid = 25134 I've been told that if I place "kernel oplocks = false" in my smb.conf file, I won't see this message any more. However, if I do this, does

Hi there, We are thinking about sharing same files: - OS2/Win clients with Samba - Linux clients with NFS. So, the same files would be shared by 2 different protocols. Looking at the open.c samba code, there seems to be no check / no error (sharing violation) returned to the smb client when the file is already locked by an NFS client. - So, even if a file is opened and locked by an NFS client,

Am 18.08.2017 um 23:17 schrieb Jeremy Allison via samba: > This might be hidden against Windows due to directory handle leases, > which we don't yet support. Are you saying that when I replace the Samba server by a Windows SMB2 share server, I should see better performance? I can perfectly test that out and record a Wireshark trace for this if you like... Layperson question: Would

This is a new Samba config that has not yet worked. I have installed sernet-samba 4.1.14. [root at sltltfsee samba]# rpm -qa | grep sernet sernet-samba-libsmbclient0-4.1.14-10.el6.x86_64 sernet-samba-common-4.1.14-10.el6.x86_64 sernet-samba-4.1.14-10.el6.x86_64 sernet-samba-libs-4.1.14-10.el6.x86_64 sernet-samba-winbind-4.1.14-10.el6.x86_64 sernet-samba-client-4.1.14-10.el6.x86_64 I have been

Hi Previous: CentOS 6.X, samba4.x86_64 4.2.10-15.el6 Now: CentOS 7.6.1810, samba 4.8.3-4.el7 When I start smb, nmb or winbind I get no errors at all. This is all I get: May 24 22:44:04 HOST systemd[1]: Starting Samba SMB Daemon... May 24 22:44:05 HOST systemd[1]: smb.service: main process exited, code=exited, status=1/FAILURE May 24 22:44:05 HOST systemd[1]: Failed to start Samba SMB

I'm using samba version 2.2.1a on a linux RH7.2 kernel 2.4.7-10. I'm having a lot of oplock problems, specially when using office applications like word. I would like to know: 1. what is the recommended configuration in version 2.2.1a (oplocks = yes/no , level2 oplocks = yes/no , kernel oplocks = yes/no) 2. what is considered to be a stable version for oplocks usage Thanks, Nir

=================================================================== "There can't be a crisis next week. My schedule is already full." Henry A. Kissinger ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.9 include: o Sgid bit

=================================================================== "There can't be a crisis next week. My schedule is already full." Henry A. Kissinger ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.9 include: o Sgid bit