search for: nfslocking

Hello, I am attempting to reload both nfs and nfslock when changing my exports configuration file. Unfortunately, I am unable to discern the correct syntax for making a single object subscribe to multiple objects. I have tried: => [nfs nfslock] => [nfs, nfslock] => [[nfs],[nfslock]] => [[nfs] [nfslock]] and none of them seem to work. Any assistance would be appreciated. Thank

I just updated one of our servers to 5.8, and rebooted. In the logs, I saw a bunch of Mar 21 16:29:02 <server> rpc.statd[9783]: recv_rply: can't decode RPC message! Mar 21 16:29:33 <server> last message repeated 442 times Mar 21 16:30:34 <server> last message repeated 835 times Mar 21 16:31:36 <server> last message repeated 884 times Mar 21 16:32:38 <server> last

Hello, I apologize for the duplicate post, but I made a typo last time. I am trying to notify the service, not subscribe to it. Also, I found that notifying a service, in this case nfs, appears to cause the service to load even if the service is configured to be disabled. Is this supposed to happen, or should the ensure => stopped state be enforced even during a notify? Thank you, -- Rob

Hello, booting starts /etc/init.d/nfslock. today, rpc.statd used port 873. later starting xinetd finds port used and disabled rsync daemon. So its more or less a lucky break, to boot CentOS and have rsync running? In /etc/rc3.d is S14nfslock S56xinetd so by design xinetd starts always after nfslock!!!! Best regards -- Viele Gr??e i.V. Helmut Drodofsky ________________________________

Greetings, I have problem using Dom0 as NFS(v4)-server and DomU as client. When ever the client actually tries to copy data to nfs-server the virtual network (bridge) between the two hosts completely freezes and stops working. After this of course the client hangs waiting nfs-server to answer and server continues to try to contact nfslock daemon on the client. Dom0 is still accessible from

Hello all, I have been doing some searching for information about disabling services within a CentOS 5.5 install. I have found a few different opinions, and wanted to ask for some feedback. First off, the system is running a LAMP stack to serve a web application. It will only be doing email to send occasional messages out (sent via the application only). It will not be receiving email for any

Hi BTRFS community I have a problem using btrfs/nfs to store my vmware images. - following setup :(debian wheezy + backports) Linux sncubetest02 3.14-0.bpo.1-amd64 #1 SMP Debian 3.14.12-1~bpo70+1 (2014-07-13) x86_64 GNU/Linux > btrfs --version Btrfs v3.14.1 > btrfs fi show Label: none uuid: 8e37c8d0-e0ef-4857-ae9f-9a1be21901ed Total devices 2 FS bytes used 210.27GiB

*sigh* The answer is that the large exported filesystem is a very large XFS... and at least through CentOS 6, upstream has *never* fixed an NFS bug that I find, googling, being complained about in '09: it gags on inodes > 32bit (not sure if that's signed, or unsigned, but....). The answer was to either create, or find an unneeded directory with a < 32bit inode, rename the

I have this config: # BL00070 - Disable NFS service {["nfs","nfslock","netfs","portmap"]: ensure => stopped, enable => false, } user {"rpc": ensure => absent, provider => "useradd" } user {"rpcuser": ensure => absent, provider => "useradd" } file

Hi, We are running a cluster under CentOS 6.6. We recently attached a new NAS device, running CentOS 6.8 and rsync'd our user file system to it. We noticed that all the files were owned by nobody (with nobody as the group). We copied over the /etc/passwd and /etc/group files from our front-end server to our NAS server. If we log in to the NAS server we see the files owned by their

For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some

On Mon, 29 Aug 2016 18:59:31 -0400 Pat Haley wrote: > We noticed that all the files were owned by nobody Here are my notes for dealing with this issue: If all users come up as nobody on a nfs mount: Add nfs server name to the Domain = line in /etc/idmapd.conf on both the server and the clients, i.e. Domain = nameof.server /sbin/service rpcidmapd restart /sbin/service nfslock restart

Hi Just upgrading one of my dev servers - I'm replacing a current box that runs 7.3 to one that runs CentOS 4.1 Currently the 7.3 dev box talks to a fileserver also running 7.3 over NFS and that works fine. I'm now trying to get the CentOS 4.1 box to talk NFS to the 7.3 server. When i try and mount the NFS share on the CentOS box i get the following error # mount /mnt/cvs mount to

Hello, First and foremost, thanks *very* much for ctdb. It's a joy to use after banging around with other HA solutions. We're planning to use it to export Samba and NFS shares throughout campus. I'm having one problem with the NFS part though. When ctdbd first starts statd (we're using CTDB_MANAGES_NFS=yes), it does so without appending the stuff in the STATD_HOSTNAME variable

...t (I'm planning to migrate to Maildir soon), mailboxes are on an NFS filesystem. I regulary see stale dotlocks files (either from dovecot (29 bytes, hold the pid of the process) or procmail (1 byte) and processes stucked in Disk Wait state. The only way I can get ridd of them is to restart nfslocking remove the .lock file change the inode of the mailbox file locking strategies are fcntl for mbox_read in dovecot dotlock fcntl for mbox_write in dovecot dotlock fcntl for procmail so I can't figure out why I see such stale locks and processes. Note : I disabled nfs attribute caching...

Hi all, I'm trying to setup this scenario on NFS and autofs on Centos 4.3: - useradd nfstest on an NFS server (192.168.1.247) - Setting up this NFS server /etc/exports: /home/nfstest 192.168.1.252/255.255.255.0(rw,sync,no_root_squash) - useradd nfstest on a client machine (192.168.1.252) - make sure that the uid and gid are the same on the server and the client - setting up

This removes the appliance configuration bits from the installer and associated files since it has been deprecated --- installer/modules/ovirt/files/cobbler-import | 6 - .../modules/ovirt/files/ovirt-appliance-setup | 4 - installer/modules/ovirt/files/ovirt-storage | 73 ---------- installer/modules/ovirt/manifests/appliance.pp | 152 -------------------- 4 files

Thanks Jochen, no mixups present at all, file assigned to UID 501. Since this problem started few hours after the Debian upgrade, I think it is related to it. I don't know if something has changed on the NFS client side on Debian, but I don't think so as aptlistchanges didn't notify me about it, nor if Dovecot 2.2.17 treat NFS in other way. I'm stuck. On 13/07/20 16:07,

I have two RHEL4 email servers running postfix/MailScanner which use dovecot. They work great. But during bootup the nfslock script in my init.d loads rpc.statd and calls portmap to get a port number. Portmap keeps giving rpc.statd the imaps port number (993). I then have to stop my mail server services, manually start dovecot, then restart the mail server services and everything goes merrily on

Hi There is a problem when creating a domU. I intend to install Solaris N90 on RedHat RHEL5 in paravirtualized(I''ve tried fully virtualized method, that''s no problem). #xm info release : 2.6.18-53.el5xen machine : i686 xen_caps : xen-3.0-x86_32p My steps are as follow(install via NFS): 1 mkdir disk and mkdir Solaris 2 mount /dev/cdrom /disk/Solaris, it tell me that disk