每次检查nfsstat时,authrefrsh =调用:
$nfsstat -cClIEnt rpc stats:calls retrans authrefrsh280462 0 280462ClIEnt nfs v3:null getattr setattr lookup access readlink0 0% 126990 45% 0 0% 10062 3% 58592 20% 0 0%read write create mkdir symlink mknod25030 8% 0 0% 65 0% 0 0% 2 0% 0 0%remove rmdir rename link readdir readdirplus0 0% 0 0% 0 0% 0 0% 0 0% 59654 21%fsstat fsinfo pathconf commit0 0% 20 0% 10 0% 0 0%
连接细节:
$mount.nfs -v nfshost:/share/dir /somedirmount.nfs: timeout set for Tue Feb 21 18:12:18 2012mount.nfs: trying text-based options 'vers=4,addr=192.168.xx.xx,clIEntaddr=192.168.xx.xx'mount.nfs: mount(2): Operation not permittedmount.nfs: trying text-based options 'addr=192.168.xx.xx'mount.nfs: prog 100003,trying vers=3,prot=6mount.nfs: trying 192.168.xx.xx prog 100003 vers 3 prot TCP port 2049mount.nfs: prog 100005,prot=17mount.nfs: trying 192.168.xx.xx prog 100005 vers 3 prot UDP port 1011nfshost:/share/dir on /somedir type nfs
nfshost RPC环境:
$rpcinfo -T udp nfshost nfsprogram 100003 version 2 ready and waitingprogram 100003 version 3 ready and waitingprogram 100003 version 4 ready and waiting$rpcinfo -T udp nfshost mountdprogram 100005 version 1 ready and waitingprogram 100005 version 2 ready and waitingprogram 100005 version 3 ready and waiting$rpcinfo -T udp nfshost nlockmgrprogram 100021 version 1 ready and waitingrpcinfo: RPC: Program/version mismatch; low version = 1,high version = 4program 100021 version 2 is not availableprogram 100021 version 3 ready and waitingprogram 100021 version 4 ready and waiting$rpcinfo -T udp nfshost llockmgrrpcinfo: RPC: Program not registered$rpcinfo nfshostprogram version netID address service owner100000 2 tcp 0.0.0.0.0.111 portmapper unkNown100000 2 udp 0.0.0.0.0.111 portmapper unkNown100024 1 udp 0.0.0.0.2.212 status unkNown100024 1 tcp 0.0.0.0.2.215 status unkNown100021 1 udp 0.0.0.0.226.67 nlockmgr unkNown100021 3 udp 0.0.0.0.226.67 nlockmgr unkNown100021 4 udp 0.0.0.0.226.67 nlockmgr unkNown100021 1 tcp 0.0.0.0.134.55 nlockmgr unkNown100021 3 tcp 0.0.0.0.134.55 nlockmgr unkNown100021 4 tcp 0.0.0.0.134.55 nlockmgr unkNown100011 1 udp 0.0.0.0.3.230 rquotad unkNown100011 2 udp 0.0.0.0.3.230 rquotad unkNown100011 1 tcp 0.0.0.0.3.233 rquotad unkNown100011 2 tcp 0.0.0.0.3.233 rquotad unkNown100003 2 udp 0.0.0.0.8.1 nfs unkNown100003 3 udp 0.0.0.0.8.1 nfs unkNown100003 4 udp 0.0.0.0.8.1 nfs unkNown100003 2 tcp 0.0.0.0.8.1 nfs unkNown100003 3 tcp 0.0.0.0.8.1 nfs unkNown100003 4 tcp 0.0.0.0.8.1 nfs unkNown100005 1 udp 0.0.0.0.3.243 mountd unkNown100005 1 tcp 0.0.0.0.3.246 mountd unkNown100005 2 udp 0.0.0.0.3.243 mountd unkNown100005 2 tcp 0.0.0.0.3.246 mountd unkNown100005 3 udp 0.0.0.0.3.243 mountd unkNown100005 3 tcp 0.0.0.0.3.246 mountd unkNown
环境:
$uname -alinux whiteheat 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 x86_64 x86_64 x86_64 GNU/linux$mount.nfs a b -Vmount.nfs: (linux nfs-utils 1.2.4)解决方法 我在NFS中遇到了这个问题.在我的情况下问题是由于actimeo设置得太低.虽然您可能没有使用这个确切的设置,但有一整套设置可能会造成严重破坏:acregmin,acregmax,acdirmin和acdirmax.基本上发生的是系统从NFS缓存文件属性.这些设置会影响从NFS刷新之前保留文件属性的时间.在使用频繁的系统上,这些刷新变得非常明显.
另一个有问题的设置是noac.如果您使用此功能,则可以保证所有其他客户端都可以立即使用任何写入 *** 作.但是,写入将等到完成写入远程而不是使用后写.如果频繁写入NFS,这可能会使系统陷入困境.
This是一篇有趣的博客文章,他们讨论了不同的选项及其对NFS性能的影响.您还可以查看NFS的man页面以获取更多指导.不幸的是,authrefrsh可能有点像红鲱鱼,我的问题可能完全无关,尽管有类似的症状.
总结以上是内存溢出为你收集整理的是什么导致重复的linux NFS客户端RPC凭据刷新?全部内容,希望文章能够帮你解决是什么导致重复的linux NFS客户端RPC凭据刷新?所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)