From: James Pearson <james-p@moving-picture.com>
To: nfs@lists.sourceforge.net
Subject: Re: df and "Value too large for defined data type"
Date: Wed, 25 Feb 2004 22:30:47 +0000 [thread overview]
Message-ID: <403D2217.9040405@moving-picture.com> (raw)
In-Reply-To: <403B512C.66BF37BB@moving-picture.com>
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 - NFS@lists.sourceforge.net
> 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 - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-02-25 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 13:27 df and "Value too large for defined data type" James Pearson
2004-02-25 22:30 ` James Pearson [this message]
2004-02-25 22:40 ` Greg Banks
2004-02-26 10:16 ` James Pearson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403D2217.9040405@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox