Using a (vanilla) 2.6.3 NFS client and using df on a on a particular NFS
mounted file system gives:
df: `/mnt/tmp': Value too large for defined data type
/mnt/tmp is mounted from a server running 2.4.21 that has a 3.5TB RAID
split into 4 partitions of less than 1TB each. The file system on the
server is XFS.
/proc/mounts on the client shows:
lead:/disk1 /mnt/tmp nfs
rw,v3,rsize=8192,wsize=8192,hard,udp,lock,addr=lead 0 0
When I use NFSv2, df (or actually statfs()) works as expected - as do
mounts to other NFS servers (it appears to be just this one server).
Also, clients running 2.4.X, have no problems with this server.
Any ideas?
James Pearson
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
I think I've found part of the reason for this - and it's not an NFS
problem - the 'Value too large for defined data type' comes from the
'return -EOVERFLOW' from vfs_statfs_native() in fs/open.c - the value of
f_files (total number of nodes in file system) returned by FSSTAT from
the server is 2^64 - 1 (18446744073709551615) !!
It looks like 2.4.X doesn't check for this overflow - and just takes the
lower 32 bits.
The underlying remote file system is XFS - which in this case appears to
be saying that it has 2^64 - 1 inodes - which doesn't seem correct...
James Pearson
James Pearson wrote:
> Using a (vanilla) 2.6.3 NFS client and using df on a on a particular NFS
> mounted file system gives:
>
> df: `/mnt/tmp': Value too large for defined data type
>
> /mnt/tmp is mounted from a server running 2.4.21 that has a 3.5TB RAID
> split into 4 partitions of less than 1TB each. The file system on the
> server is XFS.
>
> /proc/mounts on the client shows:
>
> lead:/disk1 /mnt/tmp nfs
> rw,v3,rsize=8192,wsize=8192,hard,udp,lock,addr=lead 0 0
>
> When I use NFSv2, df (or actually statfs()) works as expected - as do
> mounts to other NFS servers (it appears to be just this one server).
>
> Also, clients running 2.4.X, have no problems with this server.
>
> Any ideas?
>
> James Pearson
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>
>
>
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Wed, Feb 25, 2004 at 10:30:47PM +0000, James Pearson wrote:
> The underlying remote file system is XFS - which in this case appears to
> be saying that it has 2^64 - 1 inodes - which doesn't seem correct...
XFS supports 64 bit inodes, so this can be correct if it's either
1. on Linux, and very recent, and mounted with the right options, or
2. on IRIX
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs