On Thu, Jun 17, 2010 at 10:42 PM, Alexander Samad <alex@xxxxxxxxxxxx> wrote: > On Tue, Jun 15, 2010 at 11:15 PM, Trond Myklebust > <trond.myklebust@xxxxxxxxxx> wrote: >> On Tue, 2010-06-15 at 12:01 +1000, Alexander Samad wrote: >>> Hi >>> >>> sorry if this is a duplicate, I have been having some problem >>> subscribing to the ml. >>> >>> >>> >>> I am having some problem with nfs-kernel on a debian amd64 (sid) i am >>> using version (1:1.2.2-1). >>> >>> when I do a tcpdump on my nfs machine and do a mount -o vers=4,udp >>> nfs:/exports/video /exports/video/ it fails >> >> UDP transport is not supported by the NFSv4 protocol. Some servers may >> allow it, but most will not. > > okay, but why does the nfs-kernel on linux look like it is sending > packets (via udp), but they are not hitting the wire. Okay I have vers=4, tcp working. But I would like to have UDP, I had issues with laptop that were asleep (hibernating) and then unable to reconnect when I restart the laptop - sometimes because the nfs server needed a reboot etc... With udp I don't have these problems. So i have done some more testing. I have enabled nfs on another server, with the same package revisions as my primary nfs server. Say server max is original nfs the one not working and nas is the newer one. if I do this on nas exportfs -o async,ro 192.168.8.0/22:/mnt/tmp I can do this on max mount -o vers=4,udp,ro,async nas:/mnt/tmp/ /mnt/tmp/ but I can't do the reverse. I have tried rebooting max into difference kernel revisions - currently using 2.6.34, tried 6.32 and 6.30 - all failed. the pain is this used to work. What I see is the same flow of packets but from max I see the outbound ack, but it doesn't hit the wire. which makes me sort of think this might not be he right ml :( but I tried different kernels.... thanks frustrated > > >> >> Cheers >> Trond >> >> > -- 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
