** Changed in: nfs-utils (Ubuntu)
       Status: New => Invalid

** Description changed:

+ Dismiss this. It was due to a faulty firmware in a Netgear ProSAFE JGS516PE 
switch discarding nfs over tcp traffic, while happily switching everything else.
+ No one else being affected pointed me to rethink the whole thing and see 
other (unless much unlikely) possibilities.
+ 
*********************************************************************************
+ 
  On all recent 3.2 and 3.8 kernels, nfs v3 shares cannot be mounted with
  tcp protocol from several nfs clients.
  
  for this test:
  nfs-kernel server 1:1.2.5-3ubuntu3.1
  kernel 3.2.0-58-generic
  
  Some clients (eg. OUYA console) do mount the shares correctly, but many
  others timeout and throw a Bad file descriptor error at the console
  (tested from Android 4.3, iPad iOS 6 and Raspberry Pi Openelec Linux
  3.10.9).
  
  Even with all debug flags set to on for rpc, nfs and nfsd no output is 
produced in syslog or kern.log for a command like the following sent from a RPi 
client:
  <code>
- OpenELEC:~/mount # mount -t nfs 192.168.200.3:/media/repo1 ~/mount/repo1 -o 
nolock 
+ OpenELEC:~/mount # mount -t nfs 192.168.200.3:/media/repo1 ~/mount/repo1 -o 
nolock
  mount: RPC: Remote system error - Connection timed out
  mount: mounting 192.168.200.3:/media/repo2 on test2 failed: Bad file 
descriptor
  <code>
  
  Wireshark shows some packets coming and going from the client, including
  a portmap V2 DUMP call. When the V2 DUMP reply come back from the
  server, it has the MOUNT V3 map entry set to NO, and a FIN,ACK packet
  ends the dialog until the timeout arises at the client.
  
  Meanwhile, using proto=UDP in the mount command from the RPi gets the share 
mounted:
  <code>
  OpenELEC:~/mount # mount -t nfs 192.168.200.3:/media/repo1 ~/mount/repo1 -o 
nolock,proto=udp
  OpenELEC:~/mount #
  </code>
  and the corresponding debug info is written to the kern.log
  <code>
  Jan  3 18:35:58 Zuncho kernel: [ 5613.283291] nfsd: exp_rootfh(/media/repo2 
[ffff88031a87b0c0] *:sdb1/2)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.283296] nfsd: fh_compose(exp 08:11/2 
///, ino=2)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290406] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), count=48, busy=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290410] svc: transport ffff8802fd35c000 
served by daemon ffff8802ce434000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290424] svc: server ffff8802ce434000, 
pool 0, transport ffff8802fd35c000, inuse=2
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290429] svc: got len=40
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290430] svc: transport ffff8802fd35c000 
served by daemon ffff8802d045c000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290440] svc: svc_authenticate (0)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290444] svc: transport ffff8802fd35c000 
busy, not enqueued
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290445] svc: calling dispatcher
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290447] nfsd_dispatch: vers 3 proc 0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290450] svc: service ffff8802ce434000, 
releasing skb ffff8801f3c88900
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290459] svc: server ffff8802d045c000, 
pool 0, transport ffff8802fd35c000, inuse=3
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290465] svc: got len=-11
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290468] svc: server ffff8802d045c000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290475] svc: socket ffff8802fd35c000 
sendto([ffff8802ce6f6000 24... ], 24) = 24 (addr 192.168.200.40, port=829)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290482] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), write_space busy=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.290486] svc: server ffff8802ce434000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292130] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), count=104, busy=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292135] svc: transport ffff8802fd35c000 
served by daemon ffff8802ce434000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292149] svc: server ffff8802ce434000, 
pool 0, transport ffff8802fd35c000, inuse=2
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292154] svc: got len=96
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292155] svc: transport ffff8802fd35c000 
served by daemon ffff8802d045c000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292165] svc: svc_authenticate (1)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292172] RPC:       Want update, 
refage=120, age=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292187] svc: server ffff8802d045c000, 
pool 0, transport ffff8802fd35c000, inuse=3
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292193] svc: got len=-11
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292196] svc: server ffff8802d045c000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292345] svc: calling dispatcher
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292349] nfsd_dispatch: vers 3 proc 19
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292353] nfsd: FSINFO(3)   20: 00060001 
023938e6 2e4ff78a 67292591 a64cf247 00000000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292356] nfsd: fh_verify(20: 00060001 
023938e6 2e4ff78a 67292591 a64cf247 00000000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292360] RPC:       Want update, 
refage=120, age=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292724] found domain *
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292727] found fsidtype 6
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292728] found fsid length 16
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292731] Path seems to be </media/repo2>
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292732] Found the path /media/repo2
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292764] svc: service ffff8802ce434000, 
releasing skb ffff8801f3c88400
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292804] svc: socket ffff8802fd35c000 
sendto([ffff8802ce6f6000 80... ], 80) = 80 (addr 192.168.200.40, port=829)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292813] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), write_space busy=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.292818] svc: server ffff8802ce434000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293851] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), count=104, busy=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293855] svc: transport ffff8802fd35c000 
served by daemon ffff8802ce434000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293869] svc: server ffff8802ce434000, 
pool 0, transport ffff8802fd35c000, inuse=2
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293876] svc: got len=96
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293878] svc: transport ffff8802fd35c000 
served by daemon ffff8802d045c000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293883] svc: svc_authenticate (1)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293891] svc: transport ffff8802fd35c000 
busy, not enqueued
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293892] svc: calling dispatcher
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293893] nfsd_dispatch: vers 3 proc 1
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293897] nfsd: GETATTR(3)  20: 00060001 
023938e6 2e4ff78a 67292591 a64cf247 00000000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293899] nfsd: fh_verify(20: 00060001 
023938e6 2e4ff78a 67292591 a64cf247 00000000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293911] svc: service ffff8802ce434000, 
releasing skb ffff8801f3c88400
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293945] svc: socket ffff8802fd35c000 
sendto([ffff8802ce6f6000 112... ], 112) = 112 (addr 192.168.200.40, port=829)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293949] svc: transport ffff8802fd35c000 
busy, not enqueued
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293951] svc: server ffff8802ce434000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293954] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), write_space busy=1
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293956] svc: transport ffff8802fd35c000 
busy, not enqueued
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293959] svc: server ffff8802d045c000, 
pool 0, transport ffff8802fd35c000, inuse=2
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293961] svc: got len=-11
  Jan  3 18:35:58 Zuncho kernel: [ 5613.293963] svc: server ffff8802d045c000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.302966] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), count=104, busy=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.302971] svc: transport ffff8802fd35c000 
served by daemon ffff8802d045c000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303000] svc: server ffff8802d045c000, 
pool 0, transport ffff8802fd35c000, inuse=2
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303009] svc: got len=96
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303011] svc: transport ffff8802fd35c000 
served by daemon ffff8802ce434000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303019] svc: svc_authenticate (1)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303028] svc: transport ffff8802fd35c000 
busy, not enqueued
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303030] svc: calling dispatcher
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303031] nfsd_dispatch: vers 3 proc 19
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303035] nfsd: FSINFO(3)   20: 00060001 
023938e6 2e4ff78a 67292591 a64cf247 00000000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303037] nfsd: fh_verify(20: 00060001 
023938e6 2e4ff78a 67292591 a64cf247 00000000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303048] svc: service ffff8802d045c000, 
releasing skb ffff8801f3c88100
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303084] svc: socket ffff8802fd35c000 
sendto([ffff88031894a000 80... ], 80) = 80 (addr 192.168.200.40, port=829)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303087] svc: transport ffff8802fd35c000 
busy, not enqueued
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303089] svc: server ffff8802d045c000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303104] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), write_space busy=1
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303107] svc: transport ffff8802fd35c000 
busy, not enqueued
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303114] svc: server ffff8802ce434000, 
pool 0, transport ffff8802fd35c000, inuse=2
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303119] svc: got len=-11
  Jan  3 18:35:58 Zuncho kernel: [ 5613.303122] svc: server ffff8802ce434000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304790] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), count=104, busy=0
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304794] svc: transport ffff8802fd35c000 
served by daemon ffff8802ce434000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304826] svc: server ffff8802ce434000, 
pool 0, transport ffff8802fd35c000, inuse=2
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304834] svc: got len=96
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304836] svc: transport ffff8802fd35c000 
served by daemon ffff8802d045c000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304843] svc: svc_authenticate (1)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304852] svc: transport ffff8802fd35c000 
busy, not enqueued
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304853] svc: calling dispatcher
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304855] nfsd_dispatch: vers 3 proc 1
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304858] nfsd: GETATTR(3)  20: 00060001 
023938e6 2e4ff78a 67292591 a64cf247 00000000
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304861] nfsd: fh_verify(20: 00060001 
023938e6 2e4ff78a 67292591 a64cf247 00000000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304873] svc: service ffff8802ce434000, 
releasing skb ffff8801f3c88900
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304884] svc: server ffff8802d045c000, 
pool 0, transport ffff8802fd35c000, inuse=3
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304889] svc: got len=-11
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304892] svc: server ffff8802d045c000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304908] svc: socket ffff8802fd35c000 
sendto([ffff8802ce6f6000 112... ], 112) = 112 (addr 192.168.200.40, port=829)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304913] svc: server ffff8802ce434000 
waiting for data (to = 900000)
  Jan  3 18:35:58 Zuncho kernel: [ 5613.304915] svc: socket 
ffff8802fd35c000(inet ffff8802f24ca680), write_space busy=0
  </code>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265876

Title:
  Unable to mount nfs shares from RPi/Android/iPad clients using TCP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1265876/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to