gzip: stdout: File too large

[Carme Torca]

Hi,

I have a problem with ignite, it shows me this error after 1h 30min. of work.

* Archiving contents of openview via tar to
/var/opt/ignite/recovery/arch_mnt/2004-06-10,00:00.

gzip: stdout: File too large
ERROR: The gzip command failed (exit status 1)


The filesystem /var/opt/ignite in the ignite server is largefiles, and I have this version in gzip (in this client, and in the server is the same) : gzip 1.3.5

Maybe is there a limit in the files of ignite??
I am copying all this in the client:

Filesystem kbytes used avail %used Mounted on

/dev/vg00/lvol3 204800 165240 39360 81% /
/dev/vg00/lvol1 295024 60656 204864 23% /stand
/dev/vg00/lvol8 1560576 519448 1038256 33% /var
/dev/vg00/lvol7 2048000 1019072 1021952 50% /usr
/dev/vg00/lvol4 512000 215872 294504 42% /tmp
/dev/vg00/lvol6 4096000 2642856 1441840 65% /opt
/dev/vg00/lvol9 6144000 4879101 1189231 80% /opt/oracle
/dev/vg00/lvol5 204800 30472 173024 15% /home

Does anyone could help me??
Thanks!!
Carmen.

[Mark Grant]

Maximum size of a file for gzip is 2GB. You could consider replacing gzip wiht GNU gzip which doesn't have this limitation.

[harry d brown jr]

Mark,

gzip is GNU's gzip.

# /usr/contrib/bin/gzip -V
gzip 1.2.4 (18 Aug 93)
Compilation options:
DIRENT UTIME STDC_HEADERS HAVE_UNISTD_H
# /usr/local/bin/gzip -V
gzip 1.3.5
(2002-09-30)
Copyright 2002 Free Software Foundation
Copyright 1992-1993 Jean-loup Gailly
This program comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of this program
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
Compilation options:
DIRENT UTIME STDC_HEADERS HAVE_UNISTD_H HAVE_MEMORY_H HAVE_STRING_H HAVE_LSTAT
Written by Jean-loup Gailly.
# ls -l /usr/local/bin/gzip /usr/contrib/bin/gzip
-r-xr-xr-x 3 bin bin 139264 Nov 3 2003 /usr/contrib/bin/gzip
-rwxr-xr-x 4 root sys 81920 Sep 9 2003 /usr/local/bin/gzip
#

Carmen,

do a:

fsadm /var

on your ignite server.

And tar has a 2GB limit unless you apply the latest patches for tar.

live free or die
harry

[Fred Ruffet]

gzip stands for GNU zip, so gzip is already GNU. 1.3.5 version is the dev one. Stable release is 1.2.4. I do not consider as a good thing installing dev versions on servers. Maybe you should try to come back to a stable version, and use something like bzip2 to bypass this limitation. (note that bzip2 compresses better)

Regards,

Fred

[Mark Grant]

Doh!!!

Sometimes I wonder if that lobotomy I had was the right decision for me

[Fred Ruffet]

not sure I'll be able to gunzip it, but, reading your post I launched this test on largefile capabls FS :

#while true
>do
> echo $RANDOM
>done | gzip > tst.gz

and actually, when I have :

#du -ks tst.gz
3437256 tst.gz
this makes a 3+GB and

#gzip -V
gzip 1.2.4 (18 Aug 93)
Compilation options:
DIRENT UTIME STDC_HEADERS HAVE_UNISTD_H

So, even if my zip is not "unzipable", I didn"t have the same error...

regards,

Fred

[Victor Fridyev]

Hi,

For such big files I'd recommend
compress
which doesn't have any problem with large files.

[Fabio Ettore]

Hi Carmen,

ok gzip 1.3.5 is installed but are you sure that ignite is using that version?
gzip 1.3.5 should be put under /usr/contrib/bin, try

# /usr/contrib/bin/gzip -V

What does it obtain? 1.3.5 version?

Then make sure that gzip 1.3.5 is under /usr/local/bin (moving gzip 1.2.4 before) then relaunch ignite.

Also check this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=576751

HTH.

Best regards,
Ettore

[Patrick Wallek]

I think Ettore is right on track. Also check to make sure your file system is largefiles enabled as Harry said.

Now one thing to keep in mind is that pax has no problem CREATING a file that is larger than 2GB (how else could you use large capacity tapes?). The problem comes when you try to back up a file larger than 2GB (or 8GB with the appropriate patches). pax (and tar) simply can not handle that, but the archive itself could be 20GB as long as all the files are smaller than 2GB or 8GB (depending on patch level).

One other thing -- When using Ignite and make_net_recovery you have no control over what compression it uses. You can not tell it to use compress or bzip2 or anything else. Ignite uses gzip.

[Jeff Schussele]

To Fred Ruffet:

I would not consider a tool "stable" that can't even do the job it's designed for reliably.
gzip v1.3.1 has been released for over 2-1/2 years. For crying out loud *how* long does a version have to be released - with NO trouble reported - before it's not considered beta or development.
I sure wish the folks at HP & GNU would get off their duffs & address this problem. I think it's festered quite long enough - thank you.

My $0.02,
Jeff (To whom this is quite the sore point.)