search for: flocks

Are their issues with Samba and Lustre working together? I remember something about turning oplocks off in samba, and while testing samba I noticed this [2010/08/27 17:30:59, 3] lib/util.c:fcntl_getlock(2064) fcntl_getlock: lock request failed at offset 75694080 count 65536 type 1 (Function not implemented) But I also found out about the flock option for lustre. Should I set flock on all

Commit-ID: 11bd4ea5f3d960c4d208180deae91d88aa940149 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=11bd4ea5f3d960c4d208180deae91d88aa940149 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 21 Jan 2019 03:39:34 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 21 Jan 2019 03:45:04 +0000 [klibc] fcntl: Fix struct flock

Can anyone help with some pointers to debug a problem with Samba and CTDB with smbstatus traversing the connections tdb? I've got a new two node cluster with Samba and CTDB on AIX. If I run smbstatus when the server has much user activity it hangs and the node it was run on gets banned. I see the following in the ctdb log: 2014/10/29 11:12:45.374580 [3932342]:

Hi, I'm writing an application with C under Linux and I'm trying to use the flock system function to lock a file of an NT4 Server over Samba. The problem is that the lock works well within the same machine but if it is a process on another machine (the same program) the one that tries to access the locked file, the process is not blocked until the lock is released but given full access

Dear all, > Caveats > ======= > Features which OCFS2 does not support yet: > - extended attributes > - readonly mount > - shared writeable mmap > - loopback is supported, but data written will not > be cluster coherent. > - quotas > - cluster aware flock <---------------------------------------- >

Hi, I am trying to understand file locking and share modes. I am using RedHat Enterprise Linux 4, with kernel 2.6.9-55.ELsmp, samba-3.0.10-1.4E.11 and Windows XP. In particular I am looking at a machine running Linux exporting its local filesystem using Samba, with a Windows client accessing the file share. If I use byte range locking (fcntl() on Linux, LockFile() on Windows) things work as

Hi - I'm trying to verify if OpenSSH/SFTP will in fact lock files with advisory file locking in Linux. I can test locking with the linux "flock" command to verify that file locking does work - but when I upload or download a file with SFTP it will not detect a lock. I'm asking about Linux specifically because about a year ago I was doing a similar process in Solaris 9 and

There are three applications that have their mitts on files on my mail server, which is running AIXV5.3 and UWIMAP and mbox format. The mail folders and INBOXES are native to that machine, but also are NFS exported to a login server and a mailing list server. All three machines are running the lockd daemon. Everybody wants to lock differently 1) procmail (delivering for sendmail), which

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren at togami.com

http://dovecot.org/tools/nfstest.c I wrote a test utility that tests different ways to flush NFS attribute cache and data cache. Please test in your NFS setup and show me the results, so I can make Dovecot v1.1 works well with NFS. Run the test several times (3 should be enough) to make sure the output stays the same, because the attribute cache flushes might incorrectly say "OK". And

While experimenting a bit, I found that for some reason, locking indexes with flock is problematic, but only if user is taken from passwd-file. The host system is openbsd 3.9, dovecot's configuration is added at the bottom. Authentication is from two places - first from mentioned passwd-file, then from passwd file using bsdauth (in this case, there're no problems with flock). So, if

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

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

Hi folks, I took a break from Mongrel today and instead whipped up an Atom feed generator for my site. People who love or utterly hate my essays will lover or utterly hate to subscribe to it. http://www.zedshaw.com/feed.atom Let me know if it isn''t working well in your favorite feed reader. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/

> 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 accessing files on these archive NFS shares. >> We

SUSv3 is silent on that definition, but seen several userspace software that expects flock to be defined in that file and complain that it is missing in klibc. Current declaration is in unistd.h. Signed-off-by: maximilian attems <max at stro.at> --- usr/include/sys/file.h | 9 +++++++++ usr/include/unistd.h | 1 - 2 files changed, 9 insertions(+), 1 deletions(-) create mode 100644

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

Hello, 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 accessing files on these archive NFS shares. We have done some Samba-Debugging and found out, that the call to flock in

Hi, tl;dr summary of below: flock() works, but what does it take to make sync()/fsync() work in a 3 node GFS cluster? I am under the impression that POSIX flock, POSIX fcntl(F_SETLK/F_GETLK,...), and POSIX read/write/sync/fsync are all supported in cluster operations, such that in theory, SQLite3 should be able to atomically lock the file (or a subset of page), modify pages, flush the pages to

Hi list, as I know from the README in the source files OCFS2 does not support cluster aware flock. Our web developers have to use the php flock() function. There is a second method how php can handle locking - via the fnctl() function. Will this be supportet? I assume that OCFS2 supports the c-function open() mit O_CREATE as well as O_EXCL. Am I right? Regards, Stephan