Hi, On Thu, Apr 02, 2009 at 10:57:51AM -0700, Jason Rappleye wrote: > Johann, is the update of i_size in bz 11063 causing this? We saw the > same behavior after upgrading to 1.6.7. Yes, it is likely the cause. i_size is now updated on file close on the MDT (sparse file, no data block allocated). This is done for tools like e2scan. Johann