Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #83028

Bug#1076448: linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports

Cross-posted to 2 groups.

Show all headers | View raw

Control: reassign -1 src:nfs-utils 1:1.3.4-6

Hi Haegar,

On Tue, Jul 16, 2024 at 03:56:04PM +0200, Sven-Haegar Koch wrote:
> Source: linux
> Version: 5.10.221-1
> Severity: normal
> X-Debbugs-Cc: haegar@sdinet.de
> 
> Updating from Debian Bullseye 5.10.218-1 to 5.10.221-1 broke our NFS 
> server.
> 
> The server mounts some NFS directories from a NAS, and re-exports them 
> (and more) to other servers.
> 
> With 5.10.218-1 everything worked just fine.
> 
> But with 5.10.221-1 (most likeley because of the big NFS backports in 
> 5.10.220) starting the nfs-server.service breaks with
> 
> Jul 16 12:58:56 mytest-sh exportfs[2071]: exportfs: /media/nfsroot/pvsbackup does not support NFS export
> 
> 
> We were using the normal Debian Bullseye nfs-kernel-server package:
> 
> Package: nfs-kernel-server
> Version: 1:1.3.4-6
> 
> NFS Mount via /etc/fstab:
> 10.1.2.3:/pvsbackup /media/nfsroot/pvsbackup     nfs  rw,bg,hard,timeo=600,proto=tcp,retrans=2 0 0
> 
> NFS export in /etc/exports
> /media/nfsroot/pvsbackup 10.4.5.6/32(rw,no_root_squash,no_subtree_check,fsid=61cb2589-1805-438a-9bd7-7baf0daabfd2)
> 
> 
> In the wiki page https://wiki.linux-nfs.org/wiki/index.php/NFS_re-export 
> I found the comment "You'll need nfs-utils at least 1.3.5 (specifically, 
> 3f520e8f6f5 "exportfs: Make sure pass all valid export flags to nfsd"). 
> Otherwise, on recent kernels, attempts to re-export NFS will likely 
> result in "exportfs: <path> does not support NFS export". - and the 
> Debian  Bullseye nfs-utils packages based in 1.3.4 do not satisfy this.
> 
> Seems since the NFS backports 5.10.220 can be seen as "recent kernels", 
> while the previous 5.10.218 not yet.
> 
> For testing I recompiled/backported the Debian Bookworm nfs-utils 
> 1:2.6.2-4 for Bullseye, and this totally fixes the problems.
> 
> So I think Debian Bullseye either needs these NFS kernel changes 
> reverted, or its nfs-utils/nfs-kernel-server packages updated to include 
> at least the missing commit.

Thanks for your report. Reverting the kernel changes are not an
option, as we need to follow the 5.10.y series and 5.10.220 backported
a big stack of NFS related changes. 

Would it be possible that you give the following nfs-utils package a
try and see if they fix your problem?

https://people.debian.org/~carnil/tmp/1076448/

The packages are not signed, but I have put a sha256sum.list file
along the files signed with my GPG key found in the Debian keyring.
(alternatively do rebuild the packages).

Can you report back?

Regards,
Salvatore

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1076448: linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports Sven-Haegar Koch <haegar@sdinet.de> - 2024-07-16 16:10 +0200
  Bug#1076448: linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports Salvatore Bonaccorso <carnil@debian.org> - 2024-07-16 16:50 +0200
    Bug#1076448: linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports Sven-Haegar Koch <haegar@sdinet.de> - 2024-07-16 17:10 +0200
      Bug#1076448: linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports Salvatore Bonaccorso <carnil@debian.org> - 2024-07-16 20:40 +0200
  Processed: Re: Bug#1076448: linux: Update from 5.10.218 to  5.10.221 breaks NFS re-exports "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-07-16 16:50 +0200
  Bug#1076448: marked as done (linux: Update from 5.10.218 to  5.10.221 breaks NFS re-exports) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-07-16 23:00 +0200

csiph-web