No special VM settings. The system had an uptime of 17 days.
The hardware is slightly odd, being a Zotac ZBox Nano CI320, which uses
the Intel N2930, but it's stable and I have not had any other problems
worth noting.
I upgraded and rebooted to linux-image-4.4.0-1-amd64 and now the issue
is gone. Not sure if it's because of the fresh reboot or the upgrade.
Thanks Ben
On 4/11/16 20:05, Ben Hutchings wrote:
Control: reassign -1 src:linux 4.3.3-7
Control: severity -1 normal
Control: tag -1 unreproducible moreinfo
On Mon, 2016-04-11 at 17:43 -0700, J Mo wrote:
Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: grave
Justification: renders package unusable
Relatively new system and I'm trying to get nfsd working, but it fails.
It failed for you, but generally it works.
After looking at journalctl, it seems that the nfsd module can not be loaded:
Apr 11 17:37:50.511723 myhost kernel: Installing knfsd (copyright (C) 1996
o...@monad.swb.de).
Apr 11 17:37:50.511864 myhost kernel: modprobe: page allocation failure:
order:4, mode:0x2040d0
That's an allocation of 64 KiB with mode GFP_KERNEL | __GFP_COMP |
__GFP_NOTRACK.
[...]
Apr 11 17:37:50.513675 myhost kernel: Node 0 DMA free:15896kB min:20kB low:24kB
high:28kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15984kB
managed:15900kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB
slab_reclaimable:4kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB
unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Apr 11 17:37:50.513742 myhost kernel: lowmem_reserve[]: 0 2870 7861 7861
Apr 11 17:37:50.513811 myhost kernel: Node 0 DMA32 free:703004kB min:4112kB
low:5140kB high:6168kB active_anon:13524kB inactive_anon:17448kB
active_file:500576kB inactive_file:512192kB unevictable:0kB isolated(anon):0kB
isolated(file):0kB present:3018236kB managed:2942260kB mlocked:0kB dirty:0kB
writeback:0kB mapped:16376kB shmem:5232kB slab_reclaimable:1151992kB
slab_unreclaimable:29404kB kernel_stack:1152kB pagetables:4056kB unstable:0kB
bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB
pages_scanned:0 all_unreclaimable? no
Apr 11 17:37:50.514824 myhost kernel: lowmem_reserve[]: 0 0 4990 4990
Apr 11 17:37:50.514899 myhost kernel: Node 0 Normal free:315912kB min:7152kB
low:8940kB high:10728kB active_anon:33964kB inactive_anon:21560kB
active_file:1120576kB inactive_file:1447708kB unevictable:0kB
isolated(anon):0kB isolated(file):0kB present:5242880kB managed:5110500kB
mlocked:0kB dirty:16kB writeback:0kB mapped:32176kB shmem:15280kB
slab_reclaimable:2083336kB slab_unreclaimable:48188kB kernel_stack:1440kB
pagetables:6980kB unstable:0kB bounce:0kB free_pcp:188kB local_pcp:0kB
free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Apr 11 17:37:50.516638 myhost kernel: lowmem_reserve[]: 0 0 0 0
Apr 11 17:37:50.516721 myhost kernel: Node 0 DMA: 2*4kB (UE) 2*8kB (UE) 2*16kB
(UE) 1*32kB (E) 3*64kB (UE) 2*128kB (UE) 2*256kB (UE) 1*512kB (E) 2*1024kB (UE)
2*2048kB (EM) 2*4096kB (M) = 15896kB
Apr 11 17:37:50.516789 myhost kernel: Node 0 DMA32: 105486*4kB (UEM) 32237*8kB
(UEM) 1411*16kB (UEM) 30*32kB (UEM) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB
0*2048kB 0*4096kB = 703376kB
Apr 11 17:37:50.516856 myhost kernel: Node 0 Normal: 64405*4kB (UEM) 6948*8kB
(UEM) 161*16kB (UEM) 5*32kB (EM) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB
0*2048kB 0*4096kB = 315940kB
Apr 11 17:37:50.516924 myhost kernel: Node 0 hugepages_total=0 hugepages_free=0
hugepages_surp=0 hugepages_size=2048kB
Apr 11 17:37:50.516992 myhost kernel: 901921 total pagecache pages
Apr 11 17:37:50.517064 myhost kernel: 1530 pages in swap cache
Apr 11 17:37:50.517128 myhost kernel: Swap cache stats: add 15480, delete
13950, find 36006575/36008881
Apr 11 17:37:50.517194 myhost kernel: Free swap = 3874448kB
Apr 11 17:37:50.517257 myhost kernel: Total swap = 3906556kB
[...]
Strange. The system had lots of RAM and swap available. The Normal
zone was fragmented so no 64 KiB blocks were immediately available, but
this allocation could have waited for defragmentation if needed.
(Such fragmentation only occurs after the system has been running for
some time, so I'm confident nfsd will successfully load if you try
loading it shortly after booting.)
Do you have any VM settings in /etc/sysctl.conf or /etc/sysctl.d?
Ben.
