On Jun 03, 2008 05:27 +0200, Nick Piggin wrote: > On Sun, Jun 01, 2008 at 09:16:02PM -0600, Andreas Dilger wrote: > > On May 30, 2008 03:14 +0200, Nick Piggin wrote: > > > Oh? Hmm, from my reading, such filesystems will already overflow f_blocks > > > check which is already there. Jon's patch only adds checks for f_bsize > > > and f_frsize. > > > > Sorry, you are right - I meant that the whole f_blocks check is broken > > for filesystems > 16TB. Scaling f_bsize is easy, and prevents gratuitous > > breakage of old applications for a few kB of accuracy. > > Oh... hmm OK but they do have stat64 I guess, although maybe they aren't > coded for it. Right - we had this problem with all of the tools with some older distros being compiled against the old statfs syscall and we had to put the statfs scaling inside Lustre to avoid the 16TB overflow. The problem with the current kernel VFS interface is that the filesystem doesn't know whether the 32-bit or 64-bit statfs interface is being called, and rather than returning an error to an application we'd prefer to return scaled statfs results (with some small amount of rounding error). Even for 20PB filesystems (the largest planned for this year) the free/used/avail space would only be rounded to 4MB sizes, which isn't so bad. > Anyway, point is noted, but I'm not the person (nor is this the patchset) > to make such changes. Right... > Do you agree that if we have these checks in coimpat_statfs, then we > should put the same ones in the non-compat as well as the 64 bit > versions? If it only affects hugetlbfs then I'm not too concerned. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
