Having an issue i believe is an NFS bug, but would like someone to verify as well as... point me the correct direction to submit a bug as needed if it indeed is. Situation: NFS server running Client connected with mounted share NFS server is shut down -- (halt or /etc/init.d/nfs stop) NFS server is turned on (booted or /etc/init.d/nfs start) Outcome: NFS client that was connected does not reconnect to that share automatically NFS client that was connected cannot reconnect via umount then mount again No other nfs client can connect to that share, before or after origial NFS clients attempts to connect/reconnect NFS clients CAN connect to a different share. Details/logs: Server shows that client is authenticating: Feb 1 03:01:47 BigBox mountd[6557]: authenticated mount request from 192.168.11.49:674 for /mnt/store/public (/mnt/store/public) Feb 1 03:01:48 BigBox mountd[6557]: authenticated mount request from 192.168.11.49:763 for /mnt/store/public (/mnt/store/public) Feb 1 03:01:50 BigBox mountd[6557]: authenticated mount request from 192.168.11.49:932 for /mnt/store/public (/mnt/store/public) Feb 1 03:01:54 BigBox mountd[6557]: authenticated mount request from 192.168.11.49:942 for /mnt/store/public (/mnt/store/public) Client shows retransmission: dylan@shobuntu:~$ sudo mount -v -t nfs bigbox:/mnt/store/public Public/ mount.nfs: timeout set for Mon Jan 31 19:09:32 2011 mount.nfs: text-based options: 'addr=192.168.11.10' mount.nfs: text-based options: 'addr=192.168.11.10' mount.nfs: text-based options: 'addr=192.168.11.10' mount.nfs: text-based options: 'addr=192.168.11.10' mount.nfs: text-based options: 'addr=192.168.11.10' Server Version: net-fs/nfs-utils Latest version available: 1.1.4-r1 Latest version installed: 1.1.4-r1 Size of files: 574 kB Homepage: http://linux-nfs.org/ Description: NFS client and server daemons License: GPL-2 (server is on Gentoo, client on Ubuntu) Thanks! Camden -- 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
