filesize limit on nfs shares?

[Jansen_8]

Hi all,

I have a problem will large files >4Gb on a NFS-share.

My NFS client is a OpenVMS 8.3 Alpha system with HP-TCPIP V5.6 ECO3

The NFS server is a Fedora 11 X86-64 (linux) system.

The share is mounted in such a way that I have read/write rights as "root" on the linux system


Than I try to create a saveset of one of my disks
i.e.
backup/log/record/image polka$dka200: foxtrot$backup:[joukj.vms_backup]disk1.bck/save

When I look with the dir/full command on the VMS system the file disk1.bck grows to the expected value (i.e. 20Gb)
When I look with the ls -al command on the linux system to the same file it appears that it only grows till around 4Gb and than stops growing.

Apparently something is wrong here. but what?
Is it a configuration problem at the server or client side?

Jouk

[Volker Halle]

Jouk,

wouldn't this be more of a question against 'ls -al' on the Linux side ?

Did you try a BACKUP/LIST of the saveset to make sure, the data has really been written and is readable ?

Or a DUMP/BLOCK=(COUNT=4,START=) disk1.bck ?

Volker.

[Jansen_8]

No, the actual size on the linux system where the file is physically located is only 4Gb. No more disk space is allocated. So the created file is not correct in some way.

[Jansen_8]

And a backup/list just gives an error as expected:

cioful-jj) backup/list DISK6_121009.BCK/save
Listing of save set(s)

%BACKUP-E-READERRS, excessive error rate reading FOXTROT$BACKUP:[JOUKJ.VMS_BACKU
P]DISK1.BCK;1
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-I-OPERSPEC
%BACKUP-I-OPERASSIST, operator assistance has been requested
%BACKUP-I-NOOPER, no operator is available to handle the request
%BACKUP-I-OPERSPEC, specify option (QUIT or CONTINUE)
Requesting PID:22008C40, Target Device:_DNFS2

[Volker Halle · Accepted solution]

Jouk,

the NFS client in TCPIP V5.6 is still V2.

The NFS Server in TCPIP V5.6 is V3. The SPD says this:

The main benefit of NFS Version 3 is increased maximum file sizeâ up to 1 terabyte for an OpenVMS file system and up to 4 gigabytes for a container file system.

This at least mentions some '4 GB' limit in the area of NFS, so this may apply to NFS client V2 as well.

Volker.

[Volker Halle]

Jouk,

from the TCPIP V5.6 Release Notes:

3.7.2 NFS Client Problems and Restrictions

. The NFS client included with TCP/IP Services uses the NFS Version 2 protocol only.
. With the NFS Version 2 protocol, the value of the file size is limited to 32 bits.

Volker.

[Jansen_8]

Thanks Volker,

That explains everything. V2 has the limit of 4Gb. So unless The IP-stack is upgraded my problem will no go away.

Jouk