This config is working fior me, with just using an older kernel. [root at mnemosyne ~]# uname -r 3.10.0-514.21.2.el7.x86_64 [root at mnemosyne ~]# rpm -qa | grep rpcbind rpcbind-0.2.0-42.el7.x86_64 [root at mnemosyne ~]# rpm -qa | grep nfs libnfsidmap-0.25-17.el7.x86_64 nfs-utils-1.3.0-0.48.el7.x86_64 Patrick -- ==================================================================| Equipe M.O.S.T. | | | Patrick BEGOU | mailto:Patrick.Begou at grenoble-inp.fr | | LEGI | | | BP 53 X | Tel 04 76 82 51 35 | | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 | ===================================================================
On 2/10/2017 11:19 ??, Patrick Begou wrote:> This config is working fior me, with just using an older kernel.Thanks Patrick, Unfortunately, it doesn't work for me. I tried booting with an older kernel (3.10.0-514.21.1.el7.x86_64) and/or downgrading rpcbind to rpcbind-0.2.0-38.el7.x86_64 (all three combinations: each one separately and both at the same time), but it didn't work. I have not tried to downgrade nfs-utils as well... Note that on the same VLAN, on the same cluster, I have another VM which I have not upgraded yet (thankfully) to 7.4 and this works normally (using 7.3 and rpcbind-0.2.0-38.el7). My findings and logs are available at: https://bugzilla.redhat.com/show_bug.cgi?id=1494834 Nick
On 2/10/2017 11:46 ??, Nikolaos Milas wrote:> Unfortunately, it doesn't work for me.Problem solved - at least in my case - by changing the NFS Export Options (of the NFS shared directory, at the data storage system) from secure to insecure. That is, I changed from: rw,no_root_squash,no_all_squash,secure,nolog to: rw,no_root_squash,no_all_squash,insecure,nolog I don't know if the behavior I had described can be explained by using the "secure" option, but after I changed to "insecure" everything works fine, using the latest packages - latest kernel and latest rpms. If anyone can provide some insight on it, that would be appreciated (since I know little about NFS). Cheers, Nick