[Bug 480444] Re: packet storm with linux NFSv4 client when calling ftruncate()

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel?  Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.7 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.  
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc6-raring/


** Tags added: kernel-da-key

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

Title:
  packet storm with linux NFSv4 client when calling ftruncate()

Status in “bzr” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Won't Fix
Status in “bzr” source package in Lucid:
  Confirmed
Status in “linux” source package in Lucid:
  Confirmed
Status in “bzr” source package in Oneiric:
  Invalid
Status in “linux” source package in Oneiric:
  Triaged

Bug description:
  linux-image-2.6.31-15-generic 2.6.31-15.49 on amd64 - bug filed
  manually through LP instead of using apport, because the bug in
  question seems to have caused apport to hang while trying to collect
  information.

  I'm recently experiencing a regression when using karmic as an NFSv4
  client with gssapi authentication.  I don't believe this problem was
  present at beta time, but I don't know if this is the result of a
  kernel change or a change in other userspace software on the client
  side.  The server hasn't changed recently, it has an uptime of 54
  days; the server is running a Linux 2.6.30 kernel.

  Share is mounted with options 'sec=krb5i,proto=tcp'.  I've tried
  modifying the mount options by adding 'soft,rsize=1024,wsize=1024';
  this doesn't appear to have any effect except to make network traces
  more readable.

  When using bzr over NFS, I'm getting random unbreakable hangs on the
  client side.  Debugging appears to show that this happens when calling
  ftruncate() (sample size == 1 - very time consuming to reproduce this
  since I have to reboot the clent each time and the client is my
  laptop).  Network traces show a crazy packet storm - 13Mbps in
  constant traffic over the wireless, pushing data at the NFS server.

  Network trace to follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/480444/+subscriptions