at or cron limitation ????

[P. Prinsloo]

I have tested this problem by writing this small script called test.sh

#!/bin/ksh
cat jas* > big2
exit 0

The listing of the jas files show that they are each 700 megs in size.
744408589 Sep 12 12:01 jas
744408589 Sep 12 12:02 jas1
744408589 Sep 12 12:03 jas2
744408589 Sep 12 12:04 jas3

If I run the manually script it runs successfully and creates a file of 2.9 gigs as per listing below.

2977634356 Sep 12 12:07 big2

But if I run the script with
at -f test.sh

it only creates a file of 2 gigs
2147483136 Sep 12 14:53 big2

Any ideas out there ?????

[Leif Halvarsson_2]

Try to log what is done.

#!/bin/ksh

for file in jas*
do
echo $file >>/tmp/filelog
cat $file
done >big2 2>/tmp/errorlog

[Chris Wilshaw]

I assume that the files are being created in the same location when you run the job manually as when it runs from cron.

If not, it could be that the filesystem that the cron job is writing to doesn't have largefiles enabled.

Check using

mkfs -m /dev/vgXX/lvolYY

This should give you something like

mkfs -F vxfs -o ninode=unlimited,bsize=1024,version=3,inosize=256,logsize=1024,largefiles /dev/vg05/lvol11 4096000

[P. Prinsloo]

Firstly yes the directory is the same in both cases and the filesystem has been created with the largfiles option.

I have created an error log

this is the output.

more /tmp/errorlog

Error 0
cat: Cannot write to output.
File too large
cat: Cannot write to output.

[Leif Halvarsson_2]

Hi
Enabling largefiles will fix it.

[Chris Wilshaw · Accepted solution]

OK,

Check out this link
http://support4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_27141&context=hpux:800:11:00


This patch has the fix you'll need.

[Dirk Wiedemann]

Hello

Chris is right.
I think the output from the errorlog says only, that /tmp hasn't enabled the largefile option and doesn't point to the original problem.

regards
Dirk

[P. Prinsloo]

thanks

The patch resolved the problem..........