>>>>> " " == Andi Kleen <ak@muc.de> writes:
> This problem already exists on 2.4. You can actually access NFS
> servers which have more than 2TB of disk space. NFS uses the
> local write size as block size. When you are lucky then
> 0xfffffffff*wsize is bigger than what your NFS server
> reports. If not you get wrong results. The only workaround
> currently is to increase wsize, but that has its limits too.
> Fixing it properly probably requires statfs64(). Any reason why
> this was not included in the sector_t patchkit ?
If fixing NFS is the main concern, and we're adding a new syscall,
could someone also add in an equivalent of the Solaris
etc. 'f_frsize'.
Reporting the underlying local filessystem block size can be of use
for some applications. On NFS this value usually differs from the
'optimal transfer block size' aka. f_bsize.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:00:28 EST