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


Groups > linux.debian.kernel > #83026 > unrolled thread

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

Started bySven-Haegar Koch <haegar@sdinet.de>
First post2024-07-16 16:10 +0200
Last post2024-07-16 23:00 +0200
Articles 6 — 3 participants

Back to article view | Back to linux.debian.kernel


Contents

  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

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

FromSven-Haegar Koch <haegar@sdinet.de>
Date2024-07-16 16:10 +0200
SubjectBug#1076448: linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports
Message-ID<J0R2p-2xzI-3@gated-at.bofh.it>
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.

Greetings,
Haegar


-- System Information:
Debian Release: 11.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), 
(500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-31-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [next] | [standalone]


#83028

FromSalvatore Bonaccorso <carnil@debian.org>
Date2024-07-16 16:50 +0200
Message-ID<J0RF7-2xMa-3@gated-at.bofh.it>
In reply to#83026
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

[toc] | [prev] | [next] | [standalone]


#83032

FromSven-Haegar Koch <haegar@sdinet.de>
Date2024-07-16 17:10 +0200
Message-ID<J0RYt-2y91-1@gated-at.bofh.it>
In reply to#83028
On Tue, 16 Jul 2024, Salvatore Bonaccorso wrote:

Moin Salvatore,

Thanks for the quick reply!

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

Sure, easy as I already setup a reproducer in some throw-away VMs
before reporting the bug.

> 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?

They work perfectly fine!

Needed to also manually install the missing libnfsidmap2 package,
but once in a real repository those dependencies will be taken
care of.

mytest-sh ~ # wget -nd https://people.debian.org/~carnil/tmp/1076448/nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb https://people.debian.org/~carnil/tmp/1076448/nfs-common_1.3.4-6+deb11u1_amd64.deb
...

mytest-sh ~ # dpkg -i nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb nfs-common_1.3.4-6+deb11u1_amd64.deb
Selecting previously unselected package nfs-kernel-server.
(Reading database ... 56033 files and directories currently installed.)
Preparing to unpack nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb ...
Unpacking nfs-kernel-server (1:1.3.4-6+deb11u1) ...
Selecting previously unselected package nfs-common.
Preparing to unpack nfs-common_1.3.4-6+deb11u1_amd64.deb ...
Unpacking nfs-common (1:1.3.4-6+deb11u1) ...
dpkg: dependency problems prevent configuration of nfs-common:
 nfs-common depends on libnfsidmap2; however:
  Package libnfsidmap2 is not installed.

dpkg: error processing package nfs-common (--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nfs-kernel-server:
 nfs-kernel-server depends on nfs-common (= 1:1.3.4-6+deb11u1); however:
  Package nfs-common is not configured yet.

dpkg: error processing package nfs-kernel-server (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.9.4-2) ...
Errors were encountered while processing:
 nfs-common
 nfs-kernel-server

mytest-sh ~ # apt install libnfsidmap2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  libnfsidmap2
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 32,6 kB of archives.
After this operation, 118 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 libnfsidmap2 amd64 0.25-6 [32,6 kB]
Fetched 32,6 kB in 0s (311 kB/s)  
Selecting previously unselected package libnfsidmap2:amd64.
(Reading database ... 56135 files and directories currently installed.)
Preparing to unpack .../libnfsidmap2_0.25-6_amd64.deb ...
Unpacking libnfsidmap2:amd64 (0.25-6) ...
Setting up libnfsidmap2:amd64 (0.25-6) ...
Setting up nfs-common (1:1.3.4-6+deb11u1) ...
Replacing config file /etc/idmapd.conf with new version
nfs-utils.service is a disabled or a static unit not running, not starting it.
Setting up nfs-kernel-server (1:1.3.4-6+deb11u1) ...
Installing new version of config file /etc/init.d/nfs-kernel-server ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u10) ...

mytest-sh ~ # dpkg -i nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb nfs-common_1.3.4-6+deb11u1_amd64.deb
(Reading database ... 56146 files and directories currently installed.)
Preparing to unpack nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb ...
Unpacking nfs-kernel-server (1:1.3.4-6+deb11u1) over (1:1.3.4-6+deb11u1) 
...
Preparing to unpack nfs-common_1.3.4-6+deb11u1_amd64.deb ...
Unpacking nfs-common (1:1.3.4-6+deb11u1) over (1:1.3.4-6+deb11u1) ...
Setting up nfs-common (1:1.3.4-6+deb11u1) ...
nfs-utils.service is a disabled or a static unit not running, not starting it.
Setting up nfs-kernel-server (1:1.3.4-6+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...

mytest-sh ~ # systemctl restart nfs-server
mytest-sh ~ #


And mount from the test client working perfectly:

mytest-eq ~ # mount -t nfs mytest-sh:/media/nfsroot/pvsbackup /mnt/tmp
mytest-eq ~ # df
...
mytest-sh:/media/nfsroot/pvsbackup 22871289344 6205200128 16666089216  28% /mnt/tmp

Thanks again for the very quick response!

c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.

[toc] | [prev] | [next] | [standalone]


#83035

FromSalvatore Bonaccorso <carnil@debian.org>
Date2024-07-16 20:40 +0200
Message-ID<J0VfH-2zWY-1@gated-at.bofh.it>
In reply to#83032
Hi,

On Tue, Jul 16, 2024 at 04:57:52PM +0200, Sven-Haegar Koch wrote:
> On Tue, 16 Jul 2024, Salvatore Bonaccorso wrote:
> 
> Moin Salvatore,
> 
> Thanks for the quick reply!

Thanks for the quick testing :)

> > Would it be possible that you give the following nfs-utils package a
> > try and see if they fix your problem?
> 
> Sure, easy as I already setup a reproducer in some throw-away VMs
> before reporting the bug.

Great!
> 
> > 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?
> 
> They work perfectly fine!
> 
> Needed to also manually install the missing libnfsidmap2 package,
> but once in a real repository those dependencies will be taken
> care of.

That are good news thank you. About the dependency, this is not a new
dependency, so if you install the packages with dependency respolving
it's all fine. 

> mytest-sh ~ # wget -nd https://people.debian.org/~carnil/tmp/1076448/nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb https://people.debian.org/~carnil/tmp/1076448/nfs-common_1.3.4-6+deb11u1_amd64.deb
> ...
> 
> mytest-sh ~ # dpkg -i nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb nfs-common_1.3.4-6+deb11u1_amd64.deb
> Selecting previously unselected package nfs-kernel-server.
> (Reading database ... 56033 files and directories currently installed.)
> Preparing to unpack nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb ...
> Unpacking nfs-kernel-server (1:1.3.4-6+deb11u1) ...
> Selecting previously unselected package nfs-common.
> Preparing to unpack nfs-common_1.3.4-6+deb11u1_amd64.deb ...
> Unpacking nfs-common (1:1.3.4-6+deb11u1) ...
> dpkg: dependency problems prevent configuration of nfs-common:
>  nfs-common depends on libnfsidmap2; however:
>   Package libnfsidmap2 is not installed.
> 
> dpkg: error processing package nfs-common (--install):
>  dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of nfs-kernel-server:
>  nfs-kernel-server depends on nfs-common (= 1:1.3.4-6+deb11u1); however:
>   Package nfs-common is not configured yet.
> 
> dpkg: error processing package nfs-kernel-server (--install):
>  dependency problems - leaving unconfigured
> Processing triggers for man-db (2.9.4-2) ...
> Errors were encountered while processing:
>  nfs-common
>  nfs-kernel-server
> 
> mytest-sh ~ # apt install libnfsidmap2
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following NEW packages will be installed:
>   libnfsidmap2
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> 2 not fully installed or removed.
> Need to get 32,6 kB of archives.
> After this operation, 118 kB of additional disk space will be used.
> Get:1 http://deb.debian.org/debian bullseye/main amd64 libnfsidmap2 amd64 0.25-6 [32,6 kB]
> Fetched 32,6 kB in 0s (311 kB/s)  
> Selecting previously unselected package libnfsidmap2:amd64.
> (Reading database ... 56135 files and directories currently installed.)
> Preparing to unpack .../libnfsidmap2_0.25-6_amd64.deb ...
> Unpacking libnfsidmap2:amd64 (0.25-6) ...
> Setting up libnfsidmap2:amd64 (0.25-6) ...
> Setting up nfs-common (1:1.3.4-6+deb11u1) ...
> Replacing config file /etc/idmapd.conf with new version
> nfs-utils.service is a disabled or a static unit not running, not starting it.
> Setting up nfs-kernel-server (1:1.3.4-6+deb11u1) ...
> Installing new version of config file /etc/init.d/nfs-kernel-server ...
> Processing triggers for man-db (2.9.4-2) ...
> Processing triggers for libc-bin (2.31-13+deb11u10) ...
> 
> mytest-sh ~ # dpkg -i nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb nfs-common_1.3.4-6+deb11u1_amd64.deb
> (Reading database ... 56146 files and directories currently installed.)
> Preparing to unpack nfs-kernel-server_1.3.4-6+deb11u1_amd64.deb ...
> Unpacking nfs-kernel-server (1:1.3.4-6+deb11u1) over (1:1.3.4-6+deb11u1) 
> ...
> Preparing to unpack nfs-common_1.3.4-6+deb11u1_amd64.deb ...
> Unpacking nfs-common (1:1.3.4-6+deb11u1) over (1:1.3.4-6+deb11u1) ...
> Setting up nfs-common (1:1.3.4-6+deb11u1) ...
> nfs-utils.service is a disabled or a static unit not running, not starting it.
> Setting up nfs-kernel-server (1:1.3.4-6+deb11u1) ...
> Processing triggers for man-db (2.9.4-2) ...
> 
> mytest-sh ~ # systemctl restart nfs-server
> mytest-sh ~ #
> 
> 
> And mount from the test client working perfectly:
> 
> mytest-eq ~ # mount -t nfs mytest-sh:/media/nfsroot/pvsbackup /mnt/tmp
> mytest-eq ~ # df
> ...
> mytest-sh:/media/nfsroot/pvsbackup 22871289344 6205200128 16666089216  28% /mnt/tmp
> 
> Thanks again for the very quick response!

So looks good. I in this case will ask the stable release managers to
accept this update for the bullseye version for the next (and last)
bullseye point release happening in august, and maybe ask if the
nfs-utils update could be accepted earlier already via the
bullseye-updates suite given the kernel change.

I will CC you on the release.debian.org bug about it.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]


#83029 — Processed: Re: Bug#1076448: linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-07-16 16:50 +0200
SubjectProcessed: Re: Bug#1076448: linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports
Message-ID<J0RF7-2xMa-5@gated-at.bofh.it>
In reply to#83026
Processing control commands:

> reassign -1 src:nfs-utils 1:1.3.4-6
Bug #1076448 [src:linux] linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports
Bug reassigned from package 'src:linux' to 'src:nfs-utils'.
No longer marked as found in versions linux/5.10.221-1.
Ignoring request to alter fixed versions of bug #1076448 to the same values previously set
Bug #1076448 [src:nfs-utils] linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports
Marked as found in versions nfs-utils/1:1.3.4-6.

-- 
1076448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076448
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#83044 — Bug#1076448: marked as done (linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-07-16 23:00 +0200
SubjectBug#1076448: marked as done (linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports)
Message-ID<J0Xrc-2BcQ-7@gated-at.bofh.it>
In reply to#83026

[Multipart message — attachments visible in raw view] — view raw

Your message dated Tue, 16 Jul 2024 20:49:15 +0000
with message-id <E1sTp6p-000XoK-A2@fasolo.debian.org>
and subject line Bug#1076448: fixed in nfs-utils 1:1.3.4-6+deb11u1
has caused the Debian Bug report #1076448,
regarding linux: Update from 5.10.218 to 5.10.221 breaks NFS re-exports
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1076448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076448
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web