* Unable to mount with udp and vers=4 screws up uid/gid [not found] <AANLkTinOBIbuEFGKbPHP95zhBtUifFpIRdxkJr8cXCvn@mail.gmail.com> @ 2010-06-14 10:34 ` Alex Samad [not found] ` <0AD72BA9-0C2D-45C7-9F80-24E407832938-SGFoFqf0RKf0CCvOHzKKcA@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Alex Samad @ 2010-06-14 10:34 UTC (permalink / raw) To: linux-nfs@vger.kernel.org > > Hi > > 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 > > > mount -o vers=3,udp nfs:/exports/video /exports/video/ > mount.nfs: mount to NFS server 'nfs:/exports/video' failed: timed > out, giving up > > > and with tcpdump, I see the request from from the client and I see the > reply ok from the nfs machine, but it seem like the nfs packet doesn't > make it to the wire, machines on the same network doesn't see the > packet. > > on the nfs server I have a bridge interface br0 => eth0 eth1 eth2 > eth3 vde0 > > on vde0 I have attached virtualbox 3.2.4, and when I look on the vde > switch with tcpdump I don't see the reply packet. > > I have done some limited testing for udp and it seems to be working, > traced dns packets > > I can mount tcp, but if I user vers4 i get wierd gid uid numbers > > ls -l > drwxrwsr-x 2 4294967294 4294967294 4.1k Oct 25 2009 Funnies > > > > rpcinfo -p > program vers proto port > 100000 2 tcp 111 portmapper > 100024 1 udp 32765 status > 100024 1 tcp 32765 status > 100021 1 udp 32768 nlockmgr > 100021 3 udp 32768 nlockmgr > 100021 4 udp 32768 nlockmgr > 100021 1 tcp 32768 nlockmgr > 100021 3 tcp 32768 nlockmgr > 100021 4 tcp 32768 nlockmgr > 100003 2 tcp 2049 nfs > 100003 3 tcp 2049 nfs > 100003 4 tcp 2049 nfs > 100227 2 tcp 2049 > 100227 3 tcp 2049 > 100003 2 udp 2049 nfs > 100003 3 udp 2049 nfs > 100003 4 udp 2049 nfs > 100227 2 udp 2049 > 100227 3 udp 2049 > 100005 1 udp 32767 mountd > 100005 1 tcp 32767 mountd > 100005 2 udp 32767 mountd > 100005 2 tcp 32767 mountd > 100005 3 udp 32767 mountd > 100005 3 tcp 32767 mountd > > on nfs restart > > Jun 13 22:05:20 max kernel: [21723.836493] svc: failed to register > lockdv1 RPC service (errno 97). > Jun 13 22:05:20 max kernel: [21723.837490] NFSD: Using > /var/lib/nfs/v4recovery as the NFSv4 state recovery directory > Jun 13 22:05:20 max kernel: [21723.837507] NFSD: starting 90-second > grace period > > > tcpdump on nfs machine of mount -o vers=4,udp nfs:/exports/video > /exports/video/ > > tcpdump -pni br0 host 192.168.10.221 and not port 22 > tcpdump: verbose output suppressed, use -v or -vv for full protocol > decode > listening on br0, link-type EN10MB (Ethernet), capture size 65535 > bytes > 22:09:12.565697 IP 192.168.10.221.30209 > 192.168.11.10.53: 52743+ A? > nfs.hme1.samad.com.au. (39) > 22:09:12.565891 IP 192.168.11.10.53 > 192.168.10.221.30209: 52743* > 2/2/3 CNAME max.lan1.hme1.samad.com.au., A 192.168.11.10 (182) > 22:09:12.567227 IP 192.168.10.221.35835 > 192.168.11.10.53: 59898+ A? > nfs.hme1.samad.com.au. (39) > 22:09:12.567369 IP 192.168.11.10.53 > 192.168.10.221.35835: 59898* > 2/2/3 CNAME max.lan1.hme1.samad.com.au., A 192.168.11.10 (182) > 22:09:12.568676 IP 192.168.10.221.243695162 > 192.168.11.10.2049: 40 > null > 22:09:12.568726 IP 192.168.11.10.2049 > 192.168.10.221.243695162: > reply ok 24 null <<<<<<<<<<<<< this is missing on the client .... > 22:09:13.668091 IP 192.168.10.221.243695162 > 192.168.11.10.2049: 40 > null > 22:09:13.668158 IP 192.168.11.10.2049 > 192.168.10.221.243695162: > reply ok 24 null > 22:09:15.867266 IP 192.168.10.221.243695162 > 192.168.11.10.2049: 40 > null > 22:09:15.867345 IP 192.168.11.10.2049 > 192.168.10.221.243695162: > reply ok 24 null > 22:09:17.680551 IP 192.168.10.221.58336 > 192.168.11.10.25826: UDP, > length 917 > > > Help :) ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <0AD72BA9-0C2D-45C7-9F80-24E407832938-SGFoFqf0RKf0CCvOHzKKcA@public.gmane.org>]
* Re: Unable to mount with udp and vers=4 screws up uid/gid [not found] ` <0AD72BA9-0C2D-45C7-9F80-24E407832938-SGFoFqf0RKf0CCvOHzKKcA@public.gmane.org> @ 2010-06-15 14:55 ` J. Bruce Fields 2010-06-17 12:52 ` Alexander Samad 0 siblings, 1 reply; 4+ messages in thread From: J. Bruce Fields @ 2010-06-15 14:55 UTC (permalink / raw) To: Alex Samad; +Cc: linux-nfs@vger.kernel.org On Mon, Jun 14, 2010 at 08:34:06PM +1000, Alex Samad wrote: > >> > >> Hi >> >> 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 >> >> >> mount -o vers=3,udp nfs:/exports/video /exports/video/ >> mount.nfs: mount to NFS server 'nfs:/exports/video' failed: timed out, >> giving up I'm confused; which are you using, v3 or v4? >> and with tcpdump, I see the request from from the client and I see the >> reply ok from the nfs machine, but it seem like the nfs packet doesn't >> make it to the wire, machines on the same network doesn't see the >> packet. >> >> on the nfs server I have a bridge interface br0 => eth0 eth1 eth2 eth3 >> vde0 >> >> on vde0 I have attached virtualbox 3.2.4, and when I look on the vde >> switch with tcpdump I don't see the reply packet. >> >> I have done some limited testing for udp and it seems to be working, >> traced dns packets >> >> I can mount tcp, but if I user vers4 i get wierd gid uid numbers I thought you said above that you *couldn't* mount v4? Apologies, I may just be sleep-deprived, but could you take just a *single* problem and describe it carefully from start to finish? >> ls -l >> drwxrwsr-x 2 4294967294 4294967294 4.1k Oct 25 2009 Funnies Probably an idmapping problem: - check that the domain in /etc/idmapd.conf is set to the same thing on client and server. - check that users have the same names on the client and on the server. --b. >> >> >> >> rpcinfo -p >> program vers proto port >> 100000 2 tcp 111 portmapper >> 100024 1 udp 32765 status >> 100024 1 tcp 32765 status >> 100021 1 udp 32768 nlockmgr >> 100021 3 udp 32768 nlockmgr >> 100021 4 udp 32768 nlockmgr >> 100021 1 tcp 32768 nlockmgr >> 100021 3 tcp 32768 nlockmgr >> 100021 4 tcp 32768 nlockmgr >> 100003 2 tcp 2049 nfs >> 100003 3 tcp 2049 nfs >> 100003 4 tcp 2049 nfs >> 100227 2 tcp 2049 >> 100227 3 tcp 2049 >> 100003 2 udp 2049 nfs >> 100003 3 udp 2049 nfs >> 100003 4 udp 2049 nfs >> 100227 2 udp 2049 >> 100227 3 udp 2049 >> 100005 1 udp 32767 mountd >> 100005 1 tcp 32767 mountd >> 100005 2 udp 32767 mountd >> 100005 2 tcp 32767 mountd >> 100005 3 udp 32767 mountd >> 100005 3 tcp 32767 mountd >> >> on nfs restart >> >> Jun 13 22:05:20 max kernel: [21723.836493] svc: failed to register >> lockdv1 RPC service (errno 97). >> Jun 13 22:05:20 max kernel: [21723.837490] NFSD: Using >> /var/lib/nfs/v4recovery as the NFSv4 state recovery directory >> Jun 13 22:05:20 max kernel: [21723.837507] NFSD: starting 90-second >> grace period >> >> >> tcpdump on nfs machine of mount -o vers=4,udp nfs:/exports/video >> /exports/video/ >> >> tcpdump -pni br0 host 192.168.10.221 and not port 22 >> tcpdump: verbose output suppressed, use -v or -vv for full protocol >> decode >> listening on br0, link-type EN10MB (Ethernet), capture size 65535 >> bytes >> 22:09:12.565697 IP 192.168.10.221.30209 > 192.168.11.10.53: 52743+ A? >> nfs.hme1.samad.com.au. (39) >> 22:09:12.565891 IP 192.168.11.10.53 > 192.168.10.221.30209: 52743* >> 2/2/3 CNAME max.lan1.hme1.samad.com.au., A 192.168.11.10 (182) >> 22:09:12.567227 IP 192.168.10.221.35835 > 192.168.11.10.53: 59898+ A? >> nfs.hme1.samad.com.au. (39) >> 22:09:12.567369 IP 192.168.11.10.53 > 192.168.10.221.35835: 59898* >> 2/2/3 CNAME max.lan1.hme1.samad.com.au., A 192.168.11.10 (182) >> 22:09:12.568676 IP 192.168.10.221.243695162 > 192.168.11.10.2049: 40 >> null >> 22:09:12.568726 IP 192.168.11.10.2049 > 192.168.10.221.243695162: >> reply ok 24 null <<<<<<<<<<<<< this is missing on the client .... >> 22:09:13.668091 IP 192.168.10.221.243695162 > 192.168.11.10.2049: 40 >> null >> 22:09:13.668158 IP 192.168.11.10.2049 > 192.168.10.221.243695162: >> reply ok 24 null >> 22:09:15.867266 IP 192.168.10.221.243695162 > 192.168.11.10.2049: 40 >> null >> 22:09:15.867345 IP 192.168.11.10.2049 > 192.168.10.221.243695162: >> reply ok 24 null >> 22:09:17.680551 IP 192.168.10.221.58336 > 192.168.11.10.25826: UDP, >> length 917 >> >> >> Help :) > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Unable to mount with udp and vers=4 screws up uid/gid 2010-06-15 14:55 ` J. Bruce Fields @ 2010-06-17 12:52 ` Alexander Samad [not found] ` <AANLkTilISmYCH2I_icpr_ka1C0wrvXLv7PFpAU925DXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Alexander Samad @ 2010-06-17 12:52 UTC (permalink / raw) To: linux-nfs@vger.kernel.org On Wed, Jun 16, 2010 at 12:55 AM, J. Bruce Fields <bfields@fieldses.org= > wrote: > On Mon, Jun 14, 2010 at 08:34:06PM +1000, Alex Samad wrote: >> >>> >> >>> Hi [snip] > > I'm confused; which are you using, v3 or v4? Sorry lots of information. I have tried several combination a) udp, vers=3D3 b) tcp, vers=3D3 c) udp, vers=3D4 d) tcp,vers=3D4 > [snip] > > I thought you said above that you *couldn't* mount v4? =A0Apologies, = I may > just be sleep-deprived, but could you take just a *single* problem an= d > describe it =A0carefully from start to finish? from the above table of combinations, currently only b & d mount with any of my clients and the nfs servers. Lets make this about option D, vers=3D4, tcp > >>> ls -l >>> drwxrwsr-x =A02 4294967294 4294967294 4.1k Oct 25 =A02009 Funnies > > Probably an idmapping problem: > > =A0 =A0 =A0 =A0- check that the domain in /etc/idmapd.conf is set to = the same > =A0 =A0 =A0 =A0 =A0thing on client and server. yes > =A0 =A0 =A0 =A0- check that users have the same names on the client a= nd on the > =A0 =A0 =A0 =A0 =A0server. yes, shared name space using ldap thanks hope that helps > > --b. > [snip] ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <AANLkTilISmYCH2I_icpr_ka1C0wrvXLv7PFpAU925DXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Unable to mount with udp and vers=4 screws up uid/gid [not found] ` <AANLkTilISmYCH2I_icpr_ka1C0wrvXLv7PFpAU925DXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2010-06-17 13:40 ` Alexander Samad 0 siblings, 0 replies; 4+ messages in thread From: Alexander Samad @ 2010-06-17 13:40 UTC (permalink / raw) To: linux-nfs@vger.kernel.org On Thu, Jun 17, 2010 at 10:52 PM, Alexander Samad <alex-SGFoFqf0RKf0CCvOHzKKcA@public.gmane.org> w= rote: > On Wed, Jun 16, 2010 at 12:55 AM, J. Bruce Fields <bfields@fieldses.o= rg> wrote: >> On Mon, Jun 14, 2010 at 08:34:06PM +1000, Alex Samad wrote: >>> >>>> >>> >>>> Hi > [snip] [snip] >> =A0 =A0 =A0 =A0- check that the domain in /etc/idmapd.conf is set to= the same >> =A0 =A0 =A0 =A0 =A0thing on client and server. > > yes idmap wasn't being started, once I started it on both servers it seems to be okay now with uid/gid > >> =A0 =A0 =A0 =A0- check that users have the same names on the client = and on the >> =A0 =A0 =A0 =A0 =A0server. > yes, shared name space using ldap > > thanks hope that helps > >> >> --b. >> > [snip] > ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-06-17 13:40 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <AANLkTinOBIbuEFGKbPHP95zhBtUifFpIRdxkJr8cXCvn@mail.gmail.com>
2010-06-14 10:34 ` Unable to mount with udp and vers=4 screws up uid/gid Alex Samad
[not found] ` <0AD72BA9-0C2D-45C7-9F80-24E407832938-SGFoFqf0RKf0CCvOHzKKcA@public.gmane.org>
2010-06-15 14:55 ` J. Bruce Fields
2010-06-17 12:52 ` Alexander Samad
[not found] ` <AANLkTilISmYCH2I_icpr_ka1C0wrvXLv7PFpAU925DXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-17 13:40 ` Alexander Samad
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox