similar to: NFS server on FreeBSD 6, client on FreeBSD 7 ?

Hello, I am attempting to get flock/file locking working between my -stable (updated ~19 may) nfs file server and -current desktop; the server is running lockd/statd, and both my mail client (mutt) and a simple perl program complain that files on the nfs server cannot be locked. I am aware that there has been work on the nfs locking code in current, and have a vague recollection of a workaround

For v1.1, probably applies to v1.0 code pretty easily too: http://hg.dovecot.org/dovecot/rev/078d9dde99c8 The other rquota patches had authunix_create_default() call. Is this needed/useful? The client is now always created+destroyed for each quota lookup. I'd think it would be faster if it was created only once, but does it then break something? If the above isn't done, clnt_create()

So I'm running nfs to get content to my web servers. Now I've had this problem 2 times (about 2 weeks since the last occurrence). I use drbd on the nfs server for redundancy. Now to my problem: All my web sites stopped responding so I started by checking dmesg and there I found a bunch of this errors || Aug 11 16:00:39 web03 kernel: lockd: server 192.168.20.22 not responding, timed out

Well, next problem. Because of samba isn't running on alphaserver 1200 with gentoo linux and kernel 2.6.9-ac12 i've simply exported my smbroot (on alpha, it is my fileserver) and have samba running on an intel pentium4 box, also gentoo, kernel 2.6.0-ac12. Seems to work, eccept some locking problems. smbd[9450]: [2005/02/08 17:29:51, 0] locking/posix.c:posix_fcntl_lock(657) smbd[9450]:

Hi, I am having problems with file locks with my NFS mounted Maildir setup. NFS Client/IMAP Server is RHEL3 clone whitebox and NFS server is a Fedora Core 2 system. Both are running lockd as far as I can tell. dovecot is installed with Dag's latest dovecot RPMs for RHEL3. Time is synced between the two systems. Here is the pertinent log file entry dovecot: Dovecot starting up Apr 7

On Sun, Jun 04, 2017 at 08:57:44AM -0400, Michael Butler wrote: > It seems that {rpc.}lockd no longer runs after the ino64 changes on any > of my systems after a full rebuild of src and ports. No log entries > offer any insight as to why :-( > > imb I don't tend to use NFS on my systems that are running head, so I haven't had occasion to test this as stated. However, I

On Tue, Feb 17, 2009 at 11:33, Alan Bartlett <ajb.stxsl at googlemail.com> wrote: > The subject line for this "conversation / thread" reads: > "Re: [CentOS-docs] [CentOS] Is the NFS lockd bug fixed ?" > The contents, however, relates to XFS & the CentOSPlus kernel. > Filipe, please take care with what you do. :-) Very sorry about that. Fixed it now. In

On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba <samba at lists.samba.org> wrote: > > I noticed a problem with time synchronization on all Windows endpoints. > I am using Samba 4.21.3 and Chrony 4.3-2. > > When I run the following command in Windows: > > w32tm /monitor > dc1.xxxx.pl *** PDC ***[192.168.45.10:123]: > ICMP: 1ms delay > NTP: +0.0000000s offset

On Mon, 20 Jan 2025 09:38:50 -0500 Jeffrey Walton via samba <samba at lists.samba.org> wrote: > On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba > <samba at lists.samba.org> wrote: > > > > I noticed a problem with time synchronization on all Windows > > endpoints. I am using Samba 4.21.3 and Chrony 4.3-2. > > > > When I run the following command

I have a bit of an oddity here: I'm using Samba 4.2.14 with AD, using Samba's internal DNS to serve to my domain (and forwarding others to Google Public DNS 8.8.8.8). However, it looks like client queries (and subsequent forwards) to a vendor's URL (www.pitneybowes.us) fail, but are successful if I query Google directly: [root at XXXX~]# nslookup -type=any www.pitneybowes.us >

I noticed a problem with time synchronization on all Windows endpoints. I am using Samba 4.21.3 and Chrony 4.3-2. When I run the following command in Windows: w32tm /monitor dc1.xxxx.pl *** PDC ***[192.168.45.10:123]: ICMP: 1ms delay NTP: +0.0000000s offset from dc1.xxxx.pl RefID: time.cloudflare.com [162.159.200.123] Stratum: 4 dc2.xxxx.pl[192.168.45.9:123]: ICMP: 1ms delay NTP: -0.0001207s

Hello. We have a number of Xen 3.4.2. boxes which have constant iowaits at around 10% with spikes up to 100% when accessing data over NFS. We have been unable to nail down the issue. Any advice? System info: release : 2.6.18-194.3.1.el5xen version : #1 SMP Thu May 13 13:49:53 EDT 2010 machine : x86_64 nr_cpus : 16 nr_nodes

On 2016-10-31 22:04, Timo Sirainen wrote: >> Oct 31 10:52:37 imap(xxx at xxxx.xx): Warning: Locking transaction log >> file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 >> seconds (syncing) >> Oct 31 10:52:37 imap(xxx at xxx.xx): Warning: Locking transaction log >> file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 >> seconds

My environment is "heterogeneous" my authentication and home server are currently stuck on a 1G shared network, the production servers and storage servers are on a bonded 40G network, all are in the same VLAN. I have about 100 servers on the 40GB bonded network each with 12cores and 128GB of memory. They are running centos 6.6 Except for my storage servers they are all just running

Hi all, I have some machines running FreeBSD and dovecot deployed. User's home dir is on NFS mount and I've found that dovecot only works with dotlock file locking mechanism, fcntl and flock failed. Now it causes problem with thunderbird (thunderbird is cachine connections) waiting forever and I noticed that dovecot is trying to acquire a lock but unsuccessful since the lock file is in

I upgraded to 2.2.26.0 and enabled count as quota backend, expecting the recent fixes to allow me to use the backend, however I get the following errors: Oct 31 10:52:13 imap(xxxx at xxxx.xx): Error: Transaction log file /mnt/nfs/xxxx.xx/xxx/indexes/dovecot.list.index.log: marked corrupted Oct 31 10:52:15 imap(xxx at xxxx.xx): Error: Transaction log file

Hi, I'm trying to setup a firewalled NFS server. I've configured my server (CentOS 5) using the following parameters /etc/sysconfig/nfs MOUNTD_NFS_V1="no" MOUNTD_NFS_V2="no" RQUOTAD_PORT=875 LOCKD_TCPPORT=32803 LOCKD_UDPPORT=32769 RPCNFSDCOUNT=64 MOUNTD_PORT=892 STATD_PORT=662 STATD_OUTGOING_PORT=2020 SECURE_NFS="yes" modprobe.conf: options lockd

hey list! I am attempting to shore up some centos machines (ranging from centos 5 to centos 5.4) for pci compliance by changing the port that nlockdmgr listens on to function under a privileged port. So what I did was try to hardcode the port by editing /etc/sysconfig/nfs # TCP port rpc.lockd should listen on. LOCKD_TCPPORT=1011 # UDP port rpc.lockd should listen on. LOCKD_UDPPORT=1011 #

We've been seeing what I gather is an old, traditional problem: kernel: lockd: server <ip address> not responding, timed out The things I've found, googling, mostly involve rebooting the NFS server, and I can't do that, it's a home directory server for a *bunch* of people, and this is only one person's workstation. Are there other solutions I haven't found yet?

Hi, somebody have an idea to make dovecot working safly with nfs without lockd ? It seems working without problem except for files ".customflags" and ".subscriptions" is exists a patch for use the dotlock locking method for these files ? Thanks, Cyril Feraudet