large file supported copy utiilty..

[Mark Henry_1]

Hi All,

I've read the white paper on large files but am no wiser as to getting a copy program which works reliably.
'cp' doesn't and I've tried cat'ing the file and redirecting to a new file, but no luck..
Any ideas?

Thx,

Mark

[Uday_S_Ankolekar]

Hi,

Did you try cpio..??

# find . -xdev|cpio -pudlmv /dst_dir

-USA..

[Sridhar Bhaskarla]

Hi Mark,

You need to go to the file system and then do a cp referencing the current directory.

#cd /file_system_where_the_file_resides
#cp -rp
./the_file /file_system_that_supports_largefiles

-Sri

[James R. Ferguson]

Hi Mark:

The standard versions of 'cpio', 'tar' and 'pax' do not support largefiles.

The is no problem with 'cp'.

As far as backup goes, 'fbackup'/'frecover' handles largefiles (>2GB). In fact, you can create a pipe using these two commands to transfer largefiles. An example from the man pages is thusly:

# fbackup -i /usr -f - | (cd /mnt; frecover -Xrf -)

Regards!

...JRF...

[Mark Henry_1]

Hi,

Thanks for the tip - no luck though - 'cpio' is one of the utilities specified as not supporting large files. I tried it but it failed..

M

[Uday_S_Ankolekar]

Hi,

Try GNUTar instead, It soupports over 2gb file.

It's avaialbale at Hp's porting site.
http://hpux.asknet.de/hppd/hpux/Gnu/tar-1.13.18

-USA..

[Mark Henry_1]

Sridhar,

I tried that but no luck..

'file too large'.

It's probably worth mentioning that the place I'm copying the file to is an nfs exported dir from an NT4 machine (hummingbird maestro).

It seems to be the copying utilities though that are throwing the errors, not the remote filesystem..

Mark

[Uday_S_Ankolekar]

Sorry ,The link I gave is no more existing !
Try this link instead..
http://hpux.connect.org.uk/

-USA.

[Sridhar Bhaskarla]

Mark,

cp should work on large files. You may want to check the limitations on NT4 as well the hummingbird's NFS?

-Sri

[Steven Sim Kok Leong]

Hi,

If your source and destination filesystem is different, check (as mentioned in above postings) that your destination filesystem supports largefiles. To check, use fsadm eg.

# fsadm -F hfs /dev/vg00/lvol1

If your source and destination filesystem is the same, one possibility is that this filesystem originally supported large files (ie. it was created or modified to accept the largefiles option) which explains why the large file resides in the filesystem. However, because you have re-modified the filesystem (fsadm) to no longer support large files, you can no longer copy (cp) it within the same filesystem.

Hope this helps. Regards.

Steven Sim Kok Leong

[Bill Hassell · Accepted solution]

You left out a very important detail: this is not an ordinary cp (and cp does indeed support copying largefiles). The detail is that the destination is not a disk at all but a special network connection to a non-HP-UX computer. Major problems ahead...

First, standard NFS cannot handle largefiles, period. This is inherent in the design and cannot be fixed. If you are running 11.0 or 11i or have the NFS version 3 patches added to your system, then you can use largefiles over an NFS v3 connection to another system running NFS v3. As far as I know, NFS on a PC does not understand NFS v3.

NFS is a poor protocol at best for file sharing and has terrible performance for large amounts of data. Use ftp instead...assuming the destination PC can handle largefiles.