NFS peculiarity

I have two Linux boxes, A and B. A NFS-exports a directory D, which B
mounts locally a mount point D'. The original directory D in A contains
(among other things) a file F that is about 4G in size. When I access the
contents of D from B (that is, when I cd into D' on B) the size of F is
listed as being 224M only.

More specifically: The difference in size as reported in A and B is
exactly 2^32 bytes. It would seem that the NFS code in my Linux boxes can
deal correctly with remote files smaller than 4G. Is this the case, or am
I doing something wrong?

In comp.os.linux.networking Augustus SFX van Dusen <(E-Mail Removed)>:
> I have two Linux boxes, A and B. A NFS-exports a directory D, which B
> mounts locally a mount point D'. The original directory D in A contains
> (among other things) a file F that is about 4G in size. When I access the
> contents of D from B (that is, when I cd into D' on B) the size of F is
> listed as being 224M only.
[..]

Sounds strange, nfs v2 supports iirc 2GB files, while v3 and v4
should just be limited by the underlying fs on the nfs server.

I'd check the version your are using or/and try mounting with a
higher version. You don't try to accidentally export some doze fs?

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 256: You need to install an RTFM interface.

On Thu, 11 May 2006 00:08:34 +0200, Michael Heiming wrote:

> In comp.os.linux.networking Augustus SFX van Dusen <(E-Mail Removed)>:
>> I have two Linux boxes, A and B. A NFS-exports a directory D,
>> which B
>> mounts locally a mount point D'. The original directory D in A contains
>> (among other things) a file F that is about 4G in size. When I access
>> the contents of D from B (that is, when I cd into D' on B) the size of F
>> is listed as being 224M only.
> [..]
>
> Sounds strange, nfs v2 supports iirc 2GB files, while v3 and v4 should
> just be limited by the underlying fs on the nfs server.
>
> I'd check the version your are using or/and try mounting with a higher
> version.

Box A uses the NFS software delivered with Slackware 10.0, whereas box B
is running Slackware 10.2. However, I noticed that the kernel running on A
was compiled with NFSv2 support only, whereas on B the kernel has NFSv3
support.

What is interesting is that in the same directory on A there is
another file, this time 3G in size, which can be seen in its entirety from
B.

> You don't try to accidentally export some doze fs?

No. Both A and B are running ext3, and the files in question are MPEG
files created on A after processing some stuff uploaded from my camcorder.

Augustus SFX van Dusen wrote:
> I have two Linux boxes, A and B. A NFS-exports a directory D, which B
> mounts locally a mount point D'. The original directory D in A contains
> (among other things) a file F that is about 4G in size. When I access the
> contents of D from B (that is, when I cd into D' on B) the size of F is
> listed as being 224M only.

Looks like a NFS userspace server and/or client compiled without LFS
support.



Igmar

In comp.os.linux.networking Augustus SFX van Dusen <(E-Mail Removed)>:
> On Thu, 11 May 2006 00:08:34 +0200, Michael Heiming wrote:

>> In comp.os.linux.networking Augustus SFX van Dusen <(E-Mail Removed)>:
>>> I have two Linux boxes, A and B. A NFS-exports a directory D,
>>> which B
>>> mounts locally a mount point D'. The original directory D in A contains
>>> (among other things) a file F that is about 4G in size. When I access
>>> the contents of D from B (that is, when I cd into D' on B) the size of F
>>> is listed as being 224M only.
>> [..]
>>
>> Sounds strange, nfs v2 supports iirc 2GB files, while v3 and v4 should
>> just be limited by the underlying fs on the nfs server.
>>
>> I'd check the version your are using or/and try mounting with a higher
>> version.

> Box A uses the NFS software delivered with Slackware 10.0, whereas box B
> is running Slackware 10.2. However, I noticed that the kernel running on A
> was compiled with NFSv2 support only, whereas on B the kernel has NFSv3
> support.

There's the problem NFSv2 does iirc just support 2GB files as
already mentioned. Upgrade/recompile you kernel and nfs-utils if
needed to get at least NFSv3 support.

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 20: divide-by-zero error