Bug#1089976: nfs-kernel-server: Fails to start - segmentation fault

[Bill Brelsford <wb@k2di.net>]

Hi Salvatore,

On Tue Dec 17 2024 at 11:12 PM +0100, Salvatore Bonaccorso wrote:
> Thanks. Unfortunately still no look in a lab setup to trigger your
> issue. When rpc.segfaults, are there any other nfs related processed
> and threads running on the system?

ps -eLf shows only one: [kworker/R-nfsiod]

> > > Can you additionally please test to downgrade to the 2.8.1-2 version
> > > and please report back if you see the problem there was well? For us
> > > it should behave actually same as 2.8.1-1 but I would like to double
> > > check.

Thanks for the pointer to snapshot.d.o.  Yes, 2.8.1-2 also has the
problem.

> > > If you start it through nfsdctl do you get the exports working?

Exports/exportfs are already working.  Trying to start with nfsdctl
instead of /etc/init.d/nfs-kernel-server (in 2.8.2-1) gives

	# nfsdctl -d autostart
	nfsdctl> autostart
	Error: Device or resource busy
	Error: Operation not permitted

> > Another possible clue: after upgrading (to 2.8.2-1), there is no
> > problem -- I can start and stop the daemon, export/unexport
> > filesystems, etc.  Everything seems normal -- until the system is
> > rebooted and rpc.nfsd is invoked.
> 
> As for the first part: What processes and kernel threads are started
> on the system at this stage?

ps -eLf gives 16 [nfsd] as well as the [kworker/R-nfsiod].  And
with the daemon started, some nfsdctl commands work:

	# nfsdctl status                 
	# nfsdctl threads  
	gracetime: 90
	leasetime: 90
	scope: k2ww
	pool-threads: 16   
	# nfsdctl listener 
	tcp:[::]:2049
	tcp:0.0.0.0:2049   
	# nfsdctl version  
	+3.0 +4.0 +4.1 +4.2

Hope this helps.  Thanks..  Bill