search for: hesperiamount2

...------------------------------------------------------------------ I tried downgrading to rpcbind-0.2.0-38.el7.x86_64 but this time it didn't help. I mount either directly: ? mount -vv -o auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 -t nfs 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2 or through /etc/fstab: ? 10.201.40.34:/data/col1/hesperia-mount?? /hesperiamount2?? nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 The box may even hung during reboot, which has never happened in the past. It needs a hard reboot (via VM admin console) to boot again. I have conf...

On 22/9/2017 2:58 ??, Nikolaos Milas wrote: > ... > or through /etc/fstab: > > ? 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2?? nfs > auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 Correction: the /etc/fstab nfs mount line has one more zero: ? 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2?? nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 I am looking forward to your feedback. B...

On 2/6/2017 10:40 ??, Philippe BOURDEU d'AGUERRE wrote: > Reverting to rpcbind-0.2.0-38.el7 solves the problem for me Thank you very much Philippe, I notice that I have upgraded to rpcbind-0.2.0-38.el7_3.x86_64 on May 26. Have you checked if this bug/behavior has been reported or should we file a bug report? Nick

...x (in order to copy data from it using rsync), it did not crash (but it only had reads and no writes in this scenario). The share was manually mounted with the following command: # mount -vv -o auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 -t nfs 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2 Questions: * Is this a known issue/bug? * Have we possibly made any NFS misconfigurations (which however have not caused any errors for about a year now)? * What could we do to prevent the error from occurring again? Please advise. Thanks, Nick