From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020613 Description of problem: After upgrading to kernel-2.4.18-5 'df' displays wrong file system size if NFS volume is larger than 2TB. Using 'strace' on 'df' demonstrates that statfs() always reports the filesystem size in 512byte blocks, i.e 2TB = 2^32 blocks. Using kernel-2.4.18-4 statfs() reports filesystem size in the same unit as the 'wsize' parameter in the mount command, most likely shifting the problem upwards by some multiplier. Version-Release number of selected component (if applicable): 2.4.18-5 How reproducible: Always Steps to Reproduce: 1.Running kernel 2.4.18-5 2.mount -o rsize=8192,wsize=8192 server:/data /data 3.df /data Actual Results: Filesystem 1k-blocks Used Available Use% Mounted on server:/data 45610944 -9223372036604093392 296293360 101% /data Expected Results: With kernel 2.4.18-4... Filesystem 1k-blocks Used Available Use% Mounted on server:/data 2193094592 1896801232 296293360 87% /data Additional info: The NFS server runs IRIX-6.5.16 and the result is the same whether the filesystem is exported with the '32bitclients' option or not. This is the full set of mount parameters. server:/data on /data type nfs \ (rw,nosuid,nodev,soft,nfsvers=3,rsize=8192,wsize=8192,addr=10.0.0.1) The following line is cut from the output of 'strace df' and will always remain the same regardless of rsize and wsize. statfs("/data", {f_type="NFS_SUPER_MAGIC", f_bsize=512, f_blocks=91221888, f_bfree=592586712, f_files=1186394032, f_ffree=1185957119, f_namelen=255}) = 0 Using NFSv2 the f_bsize is 4096 regardless of rsize and wsize. Under kernel 2.4.18-4 the f_bsize will be the same as the wsize parameter in the mount command. But trying to set it to 512 will result in f_bsize=4096. Question: How do I know what blocksize really is used?, can I trust the mount command?
support for > 2Tb filesystems has been added to the 2.5 kernel recently