File too big

[The Gunners]

Hi Everyone , looking for a dig out here please. I have a basic RP4410 Pa-Risc running HP/UX 11.11
I am trying to ftp a 3gb file from another server but it chops the ftp connection once it goes over 2gb - Im thinking I have a 'file size limit' issue here on the server. Anyone know how to get around it / is there a patch or something ? Many Thanks

[James R. Ferguson]

Hi:

The file size limitation would exist on the target server. FTP doesn't limit you.

Regards!

...JRF...

[Steven Schweda]

> The file size limitation would exist on the
> target server. FTP doesn't limit you.

Well, a file size limitation in an FTP client
or server could cause trouble.

It might be interesting to see a whole
transcript, and/or some info on "another
server".

You're on the HP-UX system, running the FTP
client, doing a "get" from "another server"?
Your local file system has large-file support
enabled?

If you can use FTP to transfer a large file
from your own server to itself, then that
would seem to shift the blame to the other
end.

[Pete Randall]

It really sounds like the destination does not have largefiles enabled. Check with fsadm:

# fsadm /tmp
fsadm: /etc/default/fs is used for determining the file system type
largefiles
#


Pete

[Fabian Briseño]

Is large files enabled on the filesystem were you are trying to copy the file?

check your /etc/fstab file for something like this

vxfs largefiles,delaylog,nodatainlog 0 2

or

you can also check is this is enabled via SAM

hope this helps.

[The Gunners]

Hi Everyone , thanks for the pointers - ah I see where the issue is - below is output of fstab -
dubhptst:etc # more fstab | grep large
/dev/vg01/lvol1 /scratch vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg01/lvol2 /oracle10 vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg01/lvol3 /oracledata1 vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg02/lvol1 /oracledata2 vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg01/lvol4 /oracledata3 vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg02/lvol4 /oracledata4 vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg01/lvol5 /ua vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg02/lvol6 /sqr vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg01/lvol7 /ips vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2


can I actually 'vi' this file and change it to 'largefiles ' instead of nolargefiles ?
or is there more procedure involved to achieve this ?

[Horia Chirculescu]

Of course you can, but if your filesystem was created like this:

mkfs -F vxfs -o nolargefiles ...

Mounting the same filesystem with -o largefiles would be pointless.

Horia.

[Horia Chirculescu]

Maybe (try fsadm):

fsadm -F vxfs -o largefiles

this would help in the case I was talking about below, and the issue would not be pointless anymore

Horia

[Robert-Jan Goossens]

Hi Davey,

example

If you have OnlineJFS installed you could use:
# fsadm -F vxfs -o largefiles /home
or
# fsadm -F vxfs -o largefiles /dev/vg00/lvol5

If you do not have OnlineJFS installed you will have to unmount the filesystem and use the character device file
# umount /home
# fsadm -F vxfs -o largefiles /dev/vg00/rlvol5
# mount /home

Then change the /etc/fstab nolargefiles entry to largefiles with vi.

Regards,
Robert-Jan

[The Gunners]

Hi Horia / Robert Jan , thanks v much for the pointers - interesting outcome as it wont let me do it see below - but when I look in the /etc/fstab it is teh root inode ? Any ideas - points will eb on the way for sure on this one :P

dubhptst:etc # umount /scratch
dubhptst:etc # fsadm -F vxfs -o largefiles /dev/vg01/lvol1
vxfs fsadm: /dev/vg01/lvol1 is not the root inode of a vxfs file system
dubhptst:etc # mount /scratch
dubhptst:etc # more /etc/fstab | grep scratch
/dev/vg01/lvol1 /scratch vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2