Description of problem: Running Fedora-22 on an ARM Wandboard. Trying to set up an NFS server to share a 2TB drive connected via SATA. When the nfs servers are running at least two of them are spinning and using significant load. This load also results in missed interrupts and reduces network capability. This spinning happens regardless of whether anything is connected to the server. Version-Release number of selected component (if applicable): kernel-4.3.4-200.fc22.armv7hl nfs-utils-1.3.3-6.rc3.fc22.armv7hl How reproducible: Seems to be completely reproducible on my system. If I run: service nfs-server start it will start up and nfsd will start spinning. If I run service nfs-server stop then it will shut down and the system will run normally. Steps to Reproduce: 1. service nfs-server start 2. 3. Actual results: top - 16:19:30 up 23:36, 1 user, load average: 2.79, 2.75, 2.66 Tasks: 118 total, 5 running, 113 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.3 us, 38.5 sy, 0.0 ni, 40.7 id, 0.0 wa, 0.0 hi, 20.6 si, 0.0 st KiB Mem : 2064876 total, 62132 free, 73572 used, 1929172 buff/cache KiB Swap: 249852 total, 249432 free, 420 used. 1935800 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1024 root 20 0 0 0 0 R 77.6 0.0 1154:25 nfsd 1023 root 20 0 0 0 0 R 76.6 0.0 1150:27 nfsd 3 root 20 0 0 0 0 R 47.4 0.0 602:37.59 ksoftirqd/0 60 root 20 0 0 0 0 R 13.8 0.0 36:23.26 kswapd0 981 root 20 0 356948 29000 18440 S 4.6 1.4 158:47.23 mythbackend 13 root 20 0 0 0 0 S 1.0 0.0 10:25.97 ksoftirqd/1 18 root 20 0 0 0 0 S 1.0 0.0 9:19.12 ksoftirqd/2 8556 root 20 0 8908 3556 3060 R 1.0 0.2 0:00.16 top Expected results: nfsd shouldn't spin. Additional info: /etc/exports contains: /data 1.2.3.0/24(ro,insecure,all_squash) 192.168.1.0/24(ro,insecure,all_squash) and I added the following to the end of /etc/sysconfig/nfs: RPCNFSDCOUNT=2 LOCKD_TCPPORT=4001 LOCKD_UDPPORT=4001 MOUNTD_PORT=4002 STATD_PORT=4000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.