Ding Honghui wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1nfs server 192.168.110.28 Filesystem Size Used Avail Use% Mounted on /dev/sdb1 2.2T 1.6T 473G 78% /home /etc/exports /home/nfs_for_217 192.168.110.27/255.255.255.255 (rw,sync,no_root_squash) nfs client Filesystem Size Used Avail Use% Mounted on 192.168.110.28:/home/nfs_for_217 170G -417G 474G - /data_nfs218 What's the problem? The field Used is -417 and field Use% is -. It's really strange.. thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiEZ04ACgkQJo9Njjkvy372fgCffo9vfZra66+rRzkwiaFDeAre Rn8AmwWST1LMI/Mknc51OSgjYauCAUrl =ndad -----END PGP SIGNATURE-----
Sounds like a 32 vs. 64 bit int problem. Perhaps NFS isn't using the proper type for holding the relevant information for df to read?
If you have access to a 64 bit capable system (laptop would be easiest, you could borrow for the test), you could boot using a live 64bit Debian CD, and do a mount of the NFS filesystem there.
I expect it would show the proper sizes. -- Bob McGowan
smime.p7s
Description: S/MIME Cryptographic Signature