Created attachment 1864204 [details] Pre-upgrade package list Description of problem: After "dnf upgrade" I am unable to access any NFS shares. I use Fedora Workstation 35 on Raspberry Pi 4 (Linux 5.16.11-200.fc35.aarch64 #1 SMP Wed Feb 23 16:51:50 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux) and access NFS and CIFS shares on a QNAP NAS (TS-470 Pro). Version-Release number of selected component (if applicable): Fresh install of "Fedora-Workstation-35-1.2.aarch64" on Raspberry Pi 4 8GB libnfs.aarch64 v4.0.0-5.fc35 (not upgraded) libmount.aarch64 v2.37.4-1.fc35 (previous working version libmount.aarch64 v2.37.2-1.fc35) How reproducible: Consistent Steps to Reproduce: 1. Install Fedora Workstation 35 2. NFS share successfully mounted using "mount -t nfs <IPAddress>:/<Share> <MountPoint>" 3. Run "dnf upgrade" 4. Reboot 5. Unable to successfully mount NFS share Actual results: The command "mount -t nfs <IPAddress>:/<Share> <MountPoint>" appears to hang, does not time out, does not complete and must be manually terminated. "rpcdebug" provides no useful information, nothing is logged to the journal, the command just does not complete. Expected results: Share is successfully mounted. Additional info: "showmount" is able to successfully read a list of available shares. Other non upgraded Fedora, or non Fedora Operating Systems are successfully able to mount the share.
Created attachment 1864205 [details] Post-upgrade package list
Downgrading libmount.aarch64 v2.37.4-1.fc35 to libmount.aarch64 v2.37.2-1.fc35 does not resolve the problem. I am unsure what other packages may be involved. I have a second freshly installed SD-Card with Fedora-Workstation-35-1.2.aarch64 which I have upgraded to most recent packages available, which exhibts the same problem if you require more information from a clean system. The package lists attached are from this installation and not my original SD-Card.
Probably kernel related, maybe to do with QNAP (I have not upgraded my QNAP firmware recently). See https://bugzilla.redhat.com/show_bug.cgi?id=2055362
*** This bug has been marked as a duplicate of bug 2055362 ***