All network related bugs get assigned first to me, but this looks like NFS issue Begin forwarded message: Date: Tue, 22 Dec 2015 15:46:25 +0000 From: "bugzilla-daemon@xxxxxxxxxxxxxxxxxxx" <bugzilla-daemon@xxxxxxxxxxxxxxxxxxx> To: "shemminger@xxxxxxxxxxxxxxxxxxxx" <shemminger@xxxxxxxxxxxxxxxxxxxx> Subject: [Bug 109781] New: NFS fails mount from fstab https://bugzilla.kernel.org/show_bug.cgi?id=109781 Bug ID: 109781 Summary: NFS fails mount from fstab Product: Networking Version: 2.5 Kernel Version: 4.2.7 Hardware: All OS: Linux Tree: Fedora Status: NEW Severity: normal Priority: P1 Component: Other Assignee: shemminger@xxxxxxxxxxxxxxxxxxxx Reporter: mkb@xxxxxxxxxxxx Regression: No Created attachment 198001 --> https://bugzilla.kernel.org/attachment.cgi?id=198001&action=edit grep -i nfs /var/log/messages*; [ and deleted extraneous stuff. ] I can manual mount an NFS export from another identical machine, and mounting at boot time from fstab worked under FC22. Under FC23 I can still mount NFS by hand but it fails to mount at boot time from fstab. The fstab's are identical. I used dnf-system-upgrade on the NFS server to upgrade from FC21. This worked properly and I was able to boot my (old) FC22 client with NFS mount at boot. I installed a new SSD and installed FC23 from the live DVD image on the client, and restored all the user and system config files from a backup tar (on the client). Now boot-time NFS mount fails. I still habe the old hard drive with the FC22 image that can be booted and will do the NFS boot-time mount (it is on an external USB3 drive) so we can experiment with that if necessary, but I run processes 24/7 during the week, so any experimentation would need to be done on weekends when I have down time. dmesg produced no NFS messages. Attached is a grep -i of NFS from /var/log/messages*;. -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html