search for: f_setlease

Hello, I'm using the Samba server 3.0.33 that exports volume from a GPFS. The GPFS strongly dislikes unlinking files that are locked (resulting in permission denied) using fcntl F_SETLEASE. It seems that the Samba *sometimes* tries to unlink a file that is oplocked. Why? Is this a bug? Why it does not happen always but only sometimes? I have strace logs showing: Wrong case: 8711 14:57:50.765677 open("Y_odloz/D8/D8_03_Ivet_98/06aa6459-a011-40f8-bfb1-25d15e7ada61", O_RDWR|...

..., 0x400 /* F_??? */, 0x1) = -1 EAGAIN (Resource temporarily unavailable) time(NULL) = 1150361813 geteuid32() = 1043 write(29, "[2006/06/15 10:56:53, 3] smbd/op"..., 74) = 74 geteuid32() = 1043 write(29, " linux_set_kernel_oplock: Refus"..., 229) = 229 fnctl 0x400 op seems to be F_SETLEASE. Is there a problem between the version of kernel I use and how SAMBA use F_SETLEASE ? Is there a way to resolve this problem ? Should I recompile SAMBA with specific options to fix this problem ? Best regards, -- C?dric Delfosse Linbox / Free&ALter Soft 152, r...

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 will it say "not supported" to CIFS...

...p <pid>) and see what it does. gstack <pid> also helps >often. We got the following strace over the samba process 'locked' *[PRO]* [root at pf3il0024 ~]# strace -p *38063* Process 38063 attached - interrupt to quit fcntl(39, F_SETSIG, 0x23) = 0 fcntl(39, F_SETLEASE, F_WRLCK) = 0 getxattr("tf-PRENSA_DIRLOG_20141202_100852", "system.posix_acl_access", 0x7fff5f0b8320, 132) = -1 *ENOENT* (No such file or directory) getxattr("tf-PRENSA_DIRLOG_20141202_100852", "system.posix_acl_access", 0x7fff5f0b8310, 132) = -1 *...

On Tue, Dec 16, 2014 at 03:40:08PM +0100, Nacho del Rey wrote: > Hi there > > In an Oracle RAC cluster using ACFS (as file-system) where we have a samba > server for sharing files to windows clients, we are suffering a strange > issue, from time to time, which it causes the Windows clients lock for a > while (10 min or a bit more) or even indefinitely when they are working >

...map > - loopback is supported, but data written will not > be cluster coherent. > - quotas > - cluster aware flock <---------------------------------------- > - Directory change notification (F_NOTIFY) > - Distributed Caching (F_SETLEASE/F_GETLEASE/break_lease) > - POSIX ACLs > - readpages / writepages (not user visible) If this is an ill-informed question, please enlighten me. I'm following this list for quite some time and have done some tests (quite some time ago) and noticed then that if you write fro...

...thing, it looks >like there's no way to do anything when the file is actually locked. Locking and share modes have bugger-all to do with leases and oplocks. Please separate the two in your mind, things will make much more sense when you do :-). >Why inotify can't be used instead of F_SETLEASE here? Because the local unix process *must* be blocked from doing *anything* to the file until the SMB client has flushed all changes back to the file. inotify just notifies, it doesn't stop any local client doing anything.

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

...: not found Checking for variable __NR_inotify_init : not found Checking for header linux/fcntl.h : no Checking for declaration of F_SETLEASE : not found Checking for declaration of SA_SIGINFO : ok Checking for declaration of __NR_inotify_init : not found Checking for back...

...: not found Checking for variable __NR_inotify_init : not found Checking for header linux/fcntl.h : no Checking for declaration of F_SETLEASE : not found Checking for declaration of SA_SIGINFO : ok Checking for declaration of __NR_inotify_init : not found Checking for back...

Hi, These three patches fix the problems in the version two. And them base on the Tao's patches: ocfs2/xattr: xattr improvement The first patch fix some problem in xattr code. The second patch add security EA support. The third patch add ACL support. Best regards, tiger

mainly question for the intel folks, any chance to rerun the ltp testsuites to see how we are doing these days with all the changes ? thanks :) Wim

...: yes Checking for gnutls_datum : yes Checking for gnutls_datum_t : yes Checking for header linux/fcntl.h : yes Checking for declaration of F_SETLEASE : yes Checking for declaration of SA_SIGINFO : yes Checking for header execinfo.h : yes Checking for backtrace...

This patch series introduces the VHD library. It is based on the blktap2 one, with changes coming from the blktap2.5 one. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

....h usability... yes checking asm/unistd.h presence... yes checking for asm/unistd.h... yes checking sys/inotify.h usability... yes checking sys/inotify.h presence... yes checking for sys/inotify.h... yes checking for inotify_init... yes checking for __NR_inotify_init declaration... yes checking for F_SETLEASE declaration... yes checking for SA_SIGINFO declaration... yes checking configure summary... yes configure: creating build/smb_build/config.pm configure: creating config.mk configure: updating cache config.cache configure: creating ./config.status config.status: creating lib/registry/registry.pc con...