Date: Mon, 29 Apr 2013 05:31:18 GMT From: Alex Strange <astrange@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/178231: 8.3 nfsv4 client reports "nfsv4 client/server protocol prob err=10026" Message-ID: <201304290531.r3T5VIbu023396@red.freebsd.org> Resent-Message-ID: <201304290540.r3T5e1Bh052104@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 178231
>Category: kern
>Synopsis: 8.3 nfsv4 client reports "nfsv4 client/server protocol prob err=10026"
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Apr 29 05:40:01 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Alex Strange
>Release: 8.3-release
>Organization:
>Environment:
FreeBSD sys 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Oct 30 02:00:23 EDT 2012 mrvacbob@sys:/usr/obj/usr/src/sys/CUSTOM amd64
>Description:
I have a busy web server which mounts two other systems over NFSv4 and writes files to them. All three systems are running FreeBSD 8.3 amd64.
dmesg frequently fills up with this:
nfsv4 client/server protocol prob err=10026
nfsv4 client/server protocol prob err=10026
…
which causes file writes to fail on specific worker processes. Killing the right process while the logging is going fixes the issue for a while, but this would cause requests to error so we'd prefer to avoid it.
nfs activity:
% nfsstat -w 1 -e
GtAttr Lookup Rdlink Read Write Rename Access Rddir
…
Client: 1106 880 0 0 424 60 880 0
Server: 0 0 0 0 0 0 0 0
nfs related sysctls:
vfs.newnfs.downdelayinitial: 12
vfs.newnfs.downdelayinterval: 30
vfs.newnfs.keytab_enctype: 1
vfs.newnfs.skip_wcc_data_onerr: 1
vfs.newnfs.nfs3_jukebox_delay: 10
vfs.newnfs.reconnects: 0
vfs.newnfs.bufpackets: 4
vfs.newnfs.callback_addr:
vfs.newnfs.nfs4acl_enable: 1
vfs.newnfs.realign_count: 0
vfs.newnfs.realign_test: 0
vfs.newnfs.nfs_directio_allow_mmap: 1
vfs.newnfs.nfs_directio_enable: 0
vfs.newnfs.clean_pages_on_close: 1
vfs.newnfs.commit_on_close: 0
vfs.newnfs.prime_access_cache: 0
vfs.newnfs.access_cache_timeout: 60
vfs.newnfs.diskless_rootpath:
vfs.newnfs.diskless_valid: 0
vfs.newnfs.nfs_ip_paranoia: 1
vfs.newnfs.defect: 0
vfs.newnfs.iodmax: 4
vfs.newnfs.iodmin: 0
vfs.newnfs.iodmaxidle: 120
vfs.newnfs.disable_checkutf8: 0
vfs.newnfs.server_max_nfsvers: 4
vfs.newnfs.server_min_nfsvers: 2
vfs.newnfs.nfs_privport: 0
vfs.newnfs.enable_locallocks: 0
vfs.newnfs.issue_delegations: 0
vfs.newnfs.commit_miss: 0
vfs.newnfs.commit_blks: 0
vfs.newnfs.mirrormnt: 1
vfs.newnfs.minthreads: 1
vfs.newnfs.maxthreads: 4
vfs.newnfs.threads: 0
vfs.newnfs.request_space_used: 0
vfs.newnfs.request_space_used_highest: 0
vfs.newnfs.request_space_high: 47185920
vfs.newnfs.request_space_low: 31457280
vfs.newnfs.request_space_throttled: 0
vfs.newnfs.request_space_throttle_count: 0
Applicable fstab:
boards:/boards /www/boards nfs rw,noatime,nfsv4,async,nolockd,late,intr,bg,timeout=5 0 0
images:/images /www/images nfs rw,noatime,nfsv4,async,nolockd,late,intr,bg,timeout=5 0 0
images:/thumbs /www/thumbs nfs rw,noatime,nfsv4,async,nolockd,late,intr,bg,timeout=5 0 0
>How-To-Repeat:
Wait.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201304290531.r3T5VIbu023396>