[Bug 1378691] Re: nfs4 id mapping unstable
Andrew
andrew2.hart at uwe.ac.uk
Thu Oct 16 11:40:02 UTC 2014
My "fix" seems to have killed something, does any one read this:
[ 3901.076315] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to linux-mm at kvack.org.
[456362.837985] ------------[ cut here ]------------
[456362.838013] WARNING: CPU: 1 PID: 5628 at /build/buildd/linux-3.13.0/fs/nfs/idmap.c:547 nfs_idmap_legacy_upcall+0x196/0x1 b0 [nfsv4]()
[456362.838015] Modules linked in: nfsv4 ppdev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 nfsd vmw_balloon auth_rpcgss nfs_acl lrw nfs gf128mul glue_helper lockd ablk_helper cryptd sunrpc fscache serio_raw parport_pc v mw_vmci lp parport mptspi mptscsih psmouse mptbase e1000 floppy
[456362.838070] CPU: 1 PID: 5628 Comm: smbd Not tainted 3.13.0-36-generic #63-Ubuntu
[456362.838072] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/09/2012
[456362.838074] 0000000000000009 ffff880099555790 ffffffff8171e569 0000000000000000
[456362.838079] ffff8800995557c8 ffffffff8106775d ffff88009af12400 000000000000000e
[456362.838082] ffff8800a3557e80 ffff8800ba319720 ffff88009af12430 ffff8800995557d8
[456362.838086] Call Trace:
[456362.838096] [<ffffffff8171e569>] dump_stack+0x45/0x56
[456362.838101] [<ffffffff8106775d>] warn_slowpath_common+0x7d/0xa0
[456362.838104] [<ffffffff8106783a>] warn_slowpath_null+0x1a/0x20
[456362.838116] [<ffffffffa023fac6>] nfs_idmap_legacy_upcall+0x196/0x1b0 [nfsv4]
[456362.838122] [<ffffffff812cdb9b>] request_key_and_link+0x34b/0x4d0
[456362.838126] [<ffffffff812ce380>] ? user_revoke+0x40/0x40
[456362.838130] [<ffffffff812c9b50>] ? keyring_alloc+0x80/0x80
[456362.838134] [<ffffffff812cddde>] request_key_with_auxdata+0x1e/0x60
[456362.838138] [<ffffffff81724da2>] ? mutex_lock+0x12/0x2f
[456362.838149] [<ffffffffa023f5f7>] nfs_idmap_get_key+0x1a7/0x1c0 [nfsv4]
[456362.838163] [<ffffffffa024004f>] nfs_map_group_to_gid+0xef/0x150 [nfsv4]
[456362.838173] [<ffffffffa02376e5>] decode_getfattr_attrs+0x1475/0x14b0 [nfsv4]
[456362.838184] [<ffffffffa02377ac>] decode_getfattr_generic.constprop.102+0x8c/0xf0 [nfsv4]
[456362.838194] [<ffffffffa0237e90>] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
[456362.838203] [<ffffffffa0237f00>] nfs4_xdr_dec_getattr+0x70/0x80 [nfsv4]
[456362.838245] [<ffffffffa00e8306>] rpcauth_unwrap_resp+0x86/0xd0 [sunrpc]
[456362.838256] [<ffffffffa0237e90>] ? nfs4_xdr_dec_access+0xa0/0xa0 [nfsv4]
[456362.838265] [<ffffffffa00daf6f>] call_decode+0x1df/0x870 [sunrpc]
[456362.838274] [<ffffffffa00dad90>] ? call_refreshresult+0x170/0x170 [sunrpc]
[456362.838282] [<ffffffffa00dad90>] ? call_refreshresult+0x170/0x170 [sunrpc]
[456362.838293] [<ffffffffa00e5d74>] __rpc_execute+0x84/0x400 [sunrpc]
[456362.838304] [<ffffffffa00e6cee>] rpc_execute+0x5e/0xa0 [sunrpc]
[456362.838313] [<ffffffffa00dd1d0>] rpc_run_task+0x70/0x90 [sunrpc]
[456362.838321] [<ffffffffa0220646>] nfs4_call_sync_sequence+0x56/0x80 [nfsv4]
[456362.838329] [<ffffffffa0220f2e>] _nfs4_proc_getattr+0xbe/0xd0 [nfsv4]
[456362.838338] [<ffffffffa022749a>] nfs4_proc_getattr+0x5a/0xd0 [nfsv4]
[456362.838367] [<ffffffffa015290f>] __nfs_revalidate_inode+0xbf/0x310 [nfs]
[456362.838376] [<ffffffffa0152c56>] nfs_revalidate_inode+0x36/0x60 [nfs]
[456362.838386] [<ffffffffa0152cd7>] nfs_getattr+0x57/0x1a0 [nfs]
[456362.838390] [<ffffffff811c1dc9>] vfs_getattr_nosec+0x29/0x40
[456362.838393] [<ffffffff811c1e9d>] vfs_getattr+0x2d/0x40
[456362.838396] [<ffffffff811c1f72>] vfs_fstatat+0x62/0xa0
[456362.838399] [<ffffffff811c2442>] SYSC_newlstat+0x22/0x40
[456362.838402] [<ffffffff811c265e>] SyS_newlstat+0xe/0x10
[456362.838406] [<ffffffff8172efad>] system_call_fastpath+0x1a/0x1f
[456362.838408] ---[ end trace 449db9ba0f587919 ]---
as a crash in nfs_idmap_legacy_upcall ?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1378691
Title:
nfs4 id mapping unstable
Status in “nfs-utils” package in Ubuntu:
New
Bug description:
Ubuntu 14.04 LTS
Mounting an NFS4 share from a EMC nas and using ldap to get ids through nsswitch.
This works but occasionally an id is lost suddenly and ls -l shows the
file owner and group as nfsnobody.
I tried using sysctl to increase kernel.keys (it didn't help)
kernel.keys.root_maxkeys = 10000
kernel.keys.root_maxbytes = 200000
kernel.keys.maxkeys = 10000
kernel.keys.maxbytes = 200000
I tried changing the timeout in /etc/request-key.d/id_resolver.conf to 10 seconds (it didn't help)
create id_resolver * * /usr/sbin/nfsidmap -t 10 %k %d
To fix the problem I have manually upgraded the kernel to
3.13.0-36-generic and I continually clear the id keys using "watch
nfsidmap -c". This seems to have reduced the problem so that I
haven't seen it so far after 2 hours.
It seems that occasionally a bad id lookup happens, and then gets
cached as bad for a very long time, and that my clearing the cache
manually gets it to do another lookup. (Does the key return bad when
it times-out instead of re-looking up?)
root# cat /proc/keys
...
29dccc9d I--Q--- 1 9m 3b010000 0 0 id_legacy uid:aj-hart at uwe.ac.uk: 5
and that the "-t 10" setting is ignored and is set to 600~9m instead.
I am hoping for a better fix than my "watch nfsidmap -c" hack if
possible.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1378691/+subscriptions
More information about the foundations-bugs
mailing list