NFSv4 stat(2) incorrect

[Scott Duckworth]

We have encountered this bug, http://www.spinics.net/lists/linux-nfs/msg17801.html, which was discussed on the linux-nfs mailing list in December 2010. I am reporting the bug here because the discussion on the linux-nfs mailing list seems to have fizzled out and resulted in nothing happening. We are seeing the problem on Ubuntu 10.04 running the 2.6.32-28-generic kernel.

Please see the above link for full details of the problem. We are able to consistently reproduce this problem exactly as described in that original problem report. The only difference is that our NFS server is a NetApp FAS 2040 running ONTAP 8.0.1, whereas the original problem report was using a Solaris NFS server.

I marked this bug as a regression since it does not affect older kernels, as described in the discussion on linux-nfs. Indeed, we do not see this problem on CentOS 5.6 running the 2.6.18-238.12.1.el5 kernel. I do not know if this bug was not present in earlier kernels in Ubuntu, as we are recent Ubuntu converts.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-generic 2.6.32.28.32
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic x86_64
NonfreeKernelModules: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs vmblock vsock vmci vmmemctl vmhgfs isofs autofs4 binfmt_misc acpiphp nfsd exportfs nfs lockd nfs_acl auth_rpcgss sunrpc snd_ens1371 gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi fbcon tileblit font bitblit ppdev softcursor snd_rawmidi psmouse serio_raw snd_seq_midi_event snd_seq parport_pc snd_timer snd_seq_device snd vga16fb vgastate soundcore snd_page_alloc i2c_piix4 shpchp intel_agp lp parport floppy mptspi e1000 mptscsih mptbase scsi_transport_spi vmxnet
Architecture: amd64
Date: Tue Sep 13 19:20:12 2011
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.3)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US
 SHELL=/bin/bash
SourcePackage: linux
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.3)
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Regression: Yes
Reproducible: Yes
Tags: lucid filesystem regression-potential needs-upstream-testing
Uname: Linux 2.6.32-28-generic x86_64
UserGroups:

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 849549

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[penalvch (penalvch)]

Scott Duckworth, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]