On 04/12/2013 09:30 PM, Andreas Radke wrote:

New stable kernels have been released.

I suggest to avoid all the NFS lost files and other trouble we've seen recently to revert the 4 NFS ACL related commits that went into 3.0.72 and 3.8.6 when updating our LTS and current kernel. If all is still fine after the bump we should inform upstream about the trouble and should try to find a proper fix.

-Andy

instead of revering the commits, I recommend to work with upstream and fix this issue once and for all.

Am Fri, 12 Apr 2013 20:30:54 +0200 schrieb Andreas Radke andyrtr@archlinux.org:

New stable kernels have been released.

I suggest to avoid all the NFS lost files and other trouble we've seen recently to revert the 4 NFS ACL related commits that went into 3.0.72 and 3.8.6 when updating our LTS and current kernel. If all is still fine after the bump we should inform upstream about the trouble and should try to find a proper fix.

-Andy

I've found the time to track this down a bit further. It's all not a bug in the kernel or NFS it seems. It's more likely a gcc compiler regression. All kernels built with gcc 4.8.0 can easily reproduce file system corruption here. I've build a 3.0.80 kernel with gcc 4.7.3 and it doesn't show this bug.

I'll bring this to the gcc bug tracker. Still no clue how to help them tracking this down further.

-Andy