RHEL6.x: nfs-kerberos fails with a permission denied error if allow_weak_crypto is disabled.ĭescription: With kinit enabled on these clients, nfs-kerberos authentication will fail and displays kinit: No supported encryption types (config file error?). Workaround: For more information, see Red Hat BUG 620502 - RHEL NFS clients disconnect from NetApp NFSv4 shares with: v4 server returned a bad sequence-id error! Checked pktt: After the client goes into a loop for write call, the storage system returns NFS4ERR_BAD_STATEID./var/log/messages:Aug 16 19:08:17 uscf1plat0 kernel: NFS: v4 server 10.113.49.8 returned a bad sequence-id error!Īug 16 19:08:17 uscf1plat0 kernel: NFS: v4 server 10.113.49.8 returned a bad sequence-id error!Īug 22 01:09:27 uscf1plat0 kernel: NFS: v4 server 10.113.49.8 returned a bad sequence-id error!.The following error messages are reported: Workaround: No workaround available in RHEL5. Upgrade the client to latest RHEL kernels like RHEL 6.6 GA which addresses this problem and has latest fixes. RHEL 5.11: "ERROR: No locks available (errno=37)" hit on NFSv3 mounts during Storage Failover operationsĭescription: RHEL 5.11 does not have the latest SUNRPC layer fixes which results "error # 37" failure. Workaround: No workaround available in RHEL5. Upgrade the client to latest RHEL kernels like RHEL 6.6 GA which addresses this problem and has latest fixes. RHEL 5.11:"EIO (errno=5)" hit on RHEL5U11 NFSv3 mounts during Storage fail over operations.ĭescription: RHEL 5.11 does not have the latest SUNRPC layer fixes which results client EIO errors. Upgrade to RHEL 6.6 GA clients which properly handle pending UNLOCK operations when performing lock recovery and all locks are cleaned up after recovery. Workaround: No workaround available in RHEL5. RHEL 5.10 and RHEL 5.11 : NLM clients can fail to recover locks with pending UNLOCK operations.ĭescription: When clients perform NLM lock recovery, RHEL 5.10 and RHEL 5.11 NLM clients can get into a state where they stop issuing pending UNLOCK operations and only reclaim existing locks, leaving the locks with pending UNLOCK operations not unlocked and not reclaimed. Workaround: Traverse to the mounted path and then use chmod, chgrp, and chown commands to work. RHEL5.9: chmod, chgrp, and chown commands fail on NFSv3 mounts. For more information, see NFSv4 'mount' command produces warnings about RPC services not running.
#NEDIT FOR WINDOWS 7 UPDATE#
Workaround: Update the nfs-utils package to version 1.0.9-66.el5 or later. RHEL5.8: Mount with sec=krb5 displays warning as ' rpc.idmapd/rpc.gssd appears not to be running'.ĭescription: Mount displays an error as ' rpc.idmapd/rpc.gssd appears not to be running' though they are running, hence nfs-kerberos fails when it is mounted with sec=krb5.