It appears the magic is all happening in /etc/init.d/nfs-kernel-server. Although, I still haven't spotted where v2 is specifically disabled. The thing that (so far) I actually got to work is to abuse RPCNFSDCOUNT in /etc/default/nfs-kernel-server, maybe because that's the only environment variable explicitly passed to rpc.nfsd.
-- Russell On Wed, Dec 18, 2024 at 2:09 PM Russell Senior <[email protected]> wrote: > > I'm in! > > Thanks for everyone's brain cells. I am incrementally smarter than before. > > -- > Russell Senior > [email protected] > > On Wed, Dec 18, 2024 at 2:00 PM Jason Bergstrom <[email protected]> wrote: > > > > https://wiki.debian.org/NFSServerSetup and rpc.nfsd man page. > > Add to /etc/default/nfs-kernel-server > > > > # Offer +v2 > > RPCNFSDOPTS="-V 2 -V 3 -V 4 -V 4.1" > > > > Jason, > > [email protected] > > > > On Wed, Dec 18, 2024 at 04:33:48PM -0500, Tomas Kuchta wrote: > > > Wouldn't you need to echo to equivalent /sys file? > > > > > > On Wed, Dec 18, 2024, 16:28 Russell Senior <[email protected]> > > > wrote: > > > > > > > I found /proc/fs/nfsd/versions contains: > > > > > > > > -2 +3 +4 +4.1 +4.2 > > > > > > > > That looks relevant. I wonder where the hell that is set? Or whether I > > > > can just echo something at it. Permissions say rw. > > > > > > > > On Wed, Dec 18, 2024 at 6:30 AM Jason Bergstrom <[email protected]> > > > > wrote: > > > > > > > > > > It will be UDP, possibly check the portmapper, too. > > > > > > > > > > I haven't used v2 since SunOS, but you could try compiling the old > > > > > nfs-user-server, or run an old OS in a VM... since you are looking for > > > > > something to do. > > > > > > > > > > Jason, > > > > > [email protected] > > > > > > > > > > On Wed, Dec 18, 2024 at 06:03:23AM -0800, Russell Senior wrote: > > > > > > My kernel config in /boot/config-5.10.0-33-amd64 has > > > > > > "CONFIG_NFSD_V2=y" ... which makes me think there is a configuration > > > > > > that has disabled v2 support despite it being available. > > > > > > > > > > > > -- > > > > > > Russell Senior > > > > > > [email protected] > > > > > > > > > > > > On Wed, Dec 18, 2024 at 5:48 AM Russell Senior > > > > > > <[email protected]> wrote: > > > > > > > > > > > > > > ... but my debian 11 server seems (according to my packet > > > > > > > capture) to > > > > > > > only support NFSv3 and NFSv4. Does anyone happen to know how to > > > > enable > > > > > > > NFSv2 on nfs-kernel-server for this device? Or have any other > > > > > > > suggested solutions to this problem? > > > > > > > > > > > > > > The device is an ancient Soekris net4826 from the mid-aughts. It > > > > > > > has > > > > > > > soldered on flash storage, so the only way to recover from > > > > > > > crashing > > > > > > > firmware is to netboot. My setup *used to* work. It's getting DHCP > > > > > > > information for PXE booting, TFTP's a kernel, but when the kernel > > > > > > > attempts to mount an nfs rootfs, the mount fails and it kernel > > > > panics. > > > > > > > We have one of them still in service in the field (and I have > > > > > > > another > > > > > > > one sitting in my test bed, crashing). > > > > > > > > > > > > > > The right solution is probably just to retire the one in the field > > > > and > > > > > > > put the whole lot of them into a "museum box", but hey, it's the > > > > > > > holidays. What better period to waste a bunch of time keeping > > > > creaking > > > > > > > hardware alive. And anyway, the museum curators will be more > > > > > > > thrilled > > > > > > > to create an exhibit if they have working firmware. > > > > > > > > > > > > > > Thanks for any clues, meanwhile I'll keep searching the interwebs. > > > > > > > > > > > > > > -- > > > > > > > Russell Senior > > > > > > > [email protected] > > > > > > > > > > > > >
