I was wrong about who was at fault here, it was the pagebuf code in
the case were we were zeroing holes in files, that path should not
touch the inode size.
Date: Sat Jul 7 06:57:13 PDT 2001
The following file(s) were checked into:
linux/fs/pagebuf/page_buf_io.c - 1.88
- when writing a sparse file, do not change the inode size when zeroing
buffers at the end of the file. This caused the linux inode size to
out of sync with the xfs inode size and confuse nfs.