similar to: I need some NFS explanations, please.

Is there an equivalent command to nfsstat -m on Centos 3.4? On solaris it reports statistics for each NFS mounted file system i.e.: /mount/point from host:/some/path Flags: vers=3,proto=tcp,sec=sys,hard,intr,link,symlink,acl,rsize=32768,wsize=32768,retrans=5,timeo=50 Attr cache: acregmin=3,acregmax=60,acdirmin=30,acdirmax=60 On a related topic, how can I make a Centos3.4 nfs server

The in-kernel nfsroot code is obsoleted by kinit. Remove it; it causes conflicts. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 161e1dc16ec1129b30b634a2a8dcbbd1937800c5 tree c30da837d746fe65d8a13ccf6f27bd381948edb4 parent 018604e070e143657abcf0cb256a1e2dda205d97 author H. Peter Anvin <hpa at zytor.com> Sat, 20 May 2006 16:24:05 -0700 committer H. Peter Anvin <hpa at

Hello I have a problem with Invalid data System debian10 dovecot-2.2.36.4 # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10 Oct 23 15:57:52 dovecot6 dovecot: lmtp(33973,media4_js,2KEXD2Dhkl+1hAAAe3x6RQ): Error: Broken file /vmail/me/media4_js/Maildir/dovecot-uidlist line 6875: Invalid data: In debian9 -

Hi I have a problem with warrnings in log Yesterday "big gays" change datastore and After this time i get warrnings in dovecot like: Warning: Created dotlock file's timestamp is different than current time (1592878268 vs 1592871191): /vmail/us/username/Maildir/dovecot-uidlist Before that there was no problem with warnnings I have dovecot director with 5 dovecot-nodes and storage

There is a conflict in glibc between <linux/in.h> and <netinet/in.h>: one defines protocols with an enum, the other does the same, but adds a self-define for every enumerated value. #define IPPROTO_IP IPPROTO_IP This means the two cannot be mixed, and since loads of include files refer to <netinet/in.h>, effectively <linux/in.h> cannot be used with glibc. Since

I'm running dovecot 2.0.16 on FreeBSD 8.2 with the mail spool and indexes on an NFS server. Lines like the following keep appearing in syslog for access to each mailbox: Error: nfs_flush_attr_cache_fd_locked: fchown(/home/philk/Mail/Deleted) failed: Bad file descriptor This is coming from nfs-workarounds.c line 210, which tracing back seems to be coming from the call to mbox_lock on

We are in the process of migrating away from Courier-IMAP/POP3 and Maildrop. I want to use Dovecot (LDA, IMAP, POP3). During my testing, it has worked great except for dotlocking on the dovecot-uidlist file. The problem: When a delivery is being made with deliver and a mail client has the mailbox open (Thunderbird in this case), neither Thunderbird or deliver can get a dotlock on the

This patch removes support for use of NFS as a root filesystem from the kernel. It also updates the documentation to reflect this. b/Documentation/nfsroot.txt | 97 +++--- b/arch/arm/def-configs/a5k | 1 b/arch/arm/def-configs/adi_evb | 1 b/arch/arm/def-configs/adsbitsy | 1 b/arch/arm/def-configs/anakin | 1

I created a centos 7 docker container in which I want to mount a NFS share in. Said share is owned by user virtual with uid 1200. So I do some exporting (docker container is in 172.17.0.0/16): spindizzy> cat /etc/exports /export 10.0.0.0/24(ro,fsid=0,no_subtree_check,sync) 172.17.0.0/16(ro,fsid=0,no_subtree_check,sync) [...] /export/mail 172.17.0.0/16(rw,root_squash,no_subtree_check,sync)

We have a 2-node Oracle RAC that keeps getting the following error: kernel: nfs: RPC call returned error 88 The storage being mounted is netapp. We don't see any errors/issues on the storage itself or the switches this client is connecting thru. The NFS network is a 2-interface ( 2 x 1Gb UTP) bond which shows no errors of any kind. We are mounting with the following mount options:

Hello! I am really need help! I am using dovecot installation on ~700 users with dspam integration via dovecot-antispam plugin. Problem in unpredictable result of moving spam-mails from INBOX to Junk and from Junk to INBOX. In some cases it works fine, but sometimes I see error like "It's not possible to move the message" in client (roundcube). Two different samples on same

We have and nfs mount from a windows pc nfs server. A file is created on the server, but can take as long as 50 seconds to become available on the client. We are running Centos 5.2 (final), using NFS version 3. Is there anything we can do from the client side to see the file more quickly. The files are very small, usually about 1k _____________________________________ "He's no

I have Solaris 10 U7 that is exporting ZFS filesytem. The client is Solaris 9 U7. I can mount the filesytem just fine but I am unable to write to it. showmount -e shows my mount is set for everyone. the dfstab file has option rw set. So what gives? Phillip -- This message posted from opensolaris.org

Commit-ID: 886783e7a10fb7a638bc6034e4cdcb6296cea6a1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=886783e7a10fb7a638bc6034e4cdcb6296cea6a1 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Oct 2019 17:18:41 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 7 Oct 2019 17:27:49 +0100 [klibc] nfsmount: Use kernel

Background: I'm new to dovecot (although with many years Washington IMAP behind me). We're considering migrating from Washington IMAP to dovecot on the main service here, and have just started trying dovecot, using RC7. Washington, IMAP has the usual(-ish) "/var/spool/mail" shared area for the INBOX (trad. UNIX "From " format); a user's folders default to being

Hello, We are having performance problems trying to migrate our pop/imap servers to a new version. Our old servers are 4 debian lenny with 5GB of RAM running of XenServer VMs with kernel 2.6.32-4-amd64 and dovecot 1.1.16. New servers are 4 ubuntu 12.04 with dovecot 2.1.5 running on vmware vm with 6 cores and 16GB of RAM and kernel 3.2.0-24-generic. On both server we are using nfs 3 with

Hi, well i mounted the OCFS drive over nfs, but it seems to have problems with it, because the NFS does not detect changes (if I add or delete files) the nfs shares still shows the old status. If i delete a file on the OCFS volume, and i am doing a "ls" on one of the nfs clients, it says for every file which was on the ocfs, "no such file or directory". Did I miss

Hello, I set up NFSv4 server. To make sure I set vfs.nfsd.server_min_nfsvers=4. I can check its version, for example, by tcpduming and then I can see in wireshark lines like: Network File System Program Version: 4 V4 Procedure: COMPOUND.... .... is there any easier way to check its version? I see there is nfsstat -e option which shows delegs and locks. But all other ones are combined with nfsv3

Hi all, I have been a loyal user of SAMBA since about 1996(?), and I recently upgraded a RH linux based system from by skipping a few generations and going directly from rh9 to FC5. Mostly everything is working, but there is an issue I haven't worked out yet with SAMBA. The main server here in our group has several shares, including some that are mounted from other servers via nfs,

I'm using a stand-alone VM server and exporting the VM files ro for MWI function only. All my registration servers mount the remote NFS share just to check MWI, all read-write functions to the VM files occur on the VM server only. On the registration servers, I mounted the remote VM share with this in my fstab.conf: 10.10.14.124:/var/spool/asterisk/voicemail /mnt/vmserver nfs