make_net_recovery fails on gzip

 
Paul Condren
Frequent Advisor

make_net_recovery fails on gzip

Hi.

I'm trying to perform a make_net_recovery of a server including just vg00 across the network to our ignite server. However after successfully creating the image the process fails and the image is deleted.

Error relates to a failure gzip'ing the image because it is too large however largefiles etc is set on the target filesystem so I am guessing that like tar, gzip has a max size limit?

Does anyone know how to resolve this? Errors are below and source OS is 11.11 and ignite server OS where files are being created is 11.23




* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/lbin/make_arch_config -c /var/opt/ignite/recovery/client_m
nt/0x001A4B074B62/recovery/2008-05-07,15:49/archive_cfg -g /var/opt/ig
nite/recovery/client_mnt/0x001A4B074B62/recovery/2008-05-07,15:49/flis
t -n 2008-05-07,15:49 -r pa -b 64 -d ira72560_image -L
/var/opt/ignite/recovery/arch_mnt -l
irb72587:/var/opt/ignite/recovery/archives/ira72560 -i 5 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Networking Archive

* /opt/ignite/data/scripts/make_sys_image -d
/var/opt/ignite/recovery/arch_mnt -t n -s local -n 2008-05-07,15:49 -m
t -w /var/opt/ignite/recovery/client_mnt/0x001A4B074B62/recovery/2008-
05-07,15:49/recovery.log -u -R -g /var/opt/ignite/recovery/client_mnt/
0x001A4B074B62/recovery/2008-05-07,15:49/flist -a 14528480

* Preparing to create a system archive.
* The archive is estimated to reach 7264240 kbytes.
* Free space on /var/opt/ignite/recovery/arch_mnt
after archive should be about 99576320 kbytes.

* Archiving contents of ira72560 via tar to
/var/opt/ignite/recovery/arch_mnt/2008-05-07,15:49.

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

ERROR: The make_sys_image command failed. The system recovery archive will
not be created.

======= 05/07/08 16:20:05 BST make_net_recovery completed unsuccessfully
LIVE ira72560 :#
7 REPLIES 7
Steven E. Protter
Exalted Contributor

Re: make_net_recovery fails on gzip

Shalom,

Few possible sources since you don't reveal the version number of Ignite.

1) The destination filesystem is not set up for largefiles. It can be modified with fsadm on the host system.
2) gzip itself is out of date and is trying to make a file greater than 2 GB. I'm not aware of a gzip version that can exceed 8 GB, and if you are trying to make an archive that big, you need to decrease the scope of the recovery and end up with a smaller image.
3) Insufficient space in the /var filesystem for the temporary files that gzip needs to make.

Check that list and make appropriate actions and check back here.

Good Luck,


>>>
* Preparing to create a system archive.
* The archive is estimated to reach 7264240 kbytes.
* Free space on /var/opt/ignite/recovery/arch_mnt
after archive should be about 99576320 kbytes.
<<<<
See item 3 above.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Dennis Handly
Acclaimed Contributor

Re: make_net_recovery fails on gzip

>I am guessing that like tar, gzip has a max size limit?
>The archive is estimated to reach 7264240 kbytes.
gzip: stdout: File too large

You are about 3.5 times too large.
gzip doesn't support large files directly.
If you use a pipe you can get it to work:
$ cat BIG | gzip | cat > BIG.gz
(The last pipe isn't needed if the result is less than 2 Gb.)

You could of course use compress(1).
Steven Schweda
Honored Contributor

Re: make_net_recovery fails on gzip

> [...] I'm not aware of a gzip version that
> can exceed 8 GB [...]

I'm not aware of a gzip version where 8GB is
any kind of special size. Old gzip versions
may have trouble with files larger than 2GB,
but if a gzip can do anything bigger than
2GB, then it won't care about things bigger
than 8GB. ("tar" is a different question.
The "tar" archive format must change (again)
to deal with file sizes bigger than 8GB, but
gzip doesn't care, because it doesn't store
the file size in the odd-ball way(s) that
"tar" does.)

Modern, large-file-capable gzip programs
abound. Version 1.3.12 seems to be current.
Getting make_sys_image to _use_ a different
(newer/better) gzip may be harder, depending
on how the script locates the gzip
executable.
Shane Seymour
Frequent Advisor

Re: make_net_recovery fails on gzip

Ignite uses gzip within a pipe (you can find where it does it in make_sys_image). Your problem appears to be one of:

1. The remote filesystem does not support large files (nolargefiles is set)
2. The remote filesystem may support large files but it may have been mounted with no large files.
3. The remote server only supports NFS v2. NFS v2 does not support large files.
4. The NFS mount has for some reason used NFS v2 when the remote system does support NFS v3.

You have some filesystem investigation and perhaps NFS troubleshooting ahead of you.
Fabien GUTIERREZ
Frequent Advisor

Re: make_net_recovery fails on gzip

gzip error may be masking in fact an error cause by tar if u got a FS larger than 8Gb check this point and if it's confirmed use the -m pax from make_net_recovery option to be able to support files larger to 8Gb
Bill Hassell
Honored Contributor

Re: make_net_recovery fails on gzip

Ignite is designed to create a recovery image for the OS, and is very poor at storing massive user or application directories. Apparently, your vg00 is extremely large so you can expect a number of problems. One is that the destination image server must have largefiles enabled. The other is that 8GB will take a VERY long time to save over the network, so long that during the backup, lots of files may get deleted, changed or moved, making the resultant backup unreliable.

Analyze you vg00 logical volumes and exclude any lvols that do not belong to the OS.


Bill Hassell, sysadmin
Steve Lewis
Honored Contributor

Re: make_net_recovery fails on gzip

check to see if you have anything in /var/adm/crash and exclude it from the ignite archive.