On Thu, Jun 07, 2012 at 11:12:02AM -0400, Bryan Schumaker wrote: > On 06/07/2012 11:04 AM, Joerg Roedel wrote: > > Can you use `mount -v` to get more output? Hmm, that is weird. When I use mount -v it actually does mount the remote NFS tree. Here is the output: root@chrom:~# mount -v lemmy:/data/repos /data/lemmy/ mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Thu Jun 7 17:21:54 2012 mount.nfs: text-based options: 'addr=165.204.15.93' mount.nfs: mount(2): Protocol not supported mount.nfs: trying 165.204.15.93 prog 100003 vers 3 prot UDP port 2049 mount.nfs: trying 165.204.15.93 prog 100005 vers 3 prot UDP port 39332 mount.nfs: text-based options (retry): 'addr=165.204.15.93,vers=3,proto=udp,mountvers=3,mountproto=udp,mountport=39332' lemmy:/data/repos on /data/lemmy type nfs (rw) When I unmount and try to mount it again without -v I still get the error message and the mount fails. With 3.4 the mount -v output is: mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Thu Jun 7 17:19:44 2012 mount.nfs: text-based options: 'addr=165.204.15.93' lemmy:/data/repos/ on /data/lemmy type nfs (rw) So for some reason the text-based options are different. Maybe that has something to do with the problem. Regards, Joerg -- 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
