Ignite server and make_sys_image

[Luke Bell]

Hello

I have encountered a problem with my ignite server and I have hit a brick wall as to what to do next ive trawelled through as many notes as i can find so appologies if this has been discussed before.

I am getting the error

gzip: stdout: I/O error
ERROR: The gzip command failed (exit status 1)
ERROR: The gzip command failed (exit status 1)

Ive run the command make_sys_image -d /ignite -s local -l1 to check that gzipo can cope with the size of the image. This works fine but it is about 6.5 GB, therefore I doubt i have a problem with gzip versions.

Further up in the log it says

* /opt/ignite/data/scripts/make_sys_image -d
/var/opt/ignite/recovery/arch_mnt -t n -s local -n 2004-02-21,04:00 -m
t -w /var/opt/ignite/recovery/client_mnt/0x00306E2C0596/recovery/2004-
02-21,04:00/recovery.log -u -R -g /var/opt/ignite/recovery/client_mnt/
0x00306E2C0596/recovery/2004-02-21,04:00/flist -a 1702240

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

There should be plentey of space even for the 6.5GB. As there doesnt seem to be either a space or gzip issue what can it be?

many thanks in advance

Luke

[Robert-Jan Goossens]

Hi Luke,

One problem could be the version of gzip, the hp gzip command does not support files > 2 GB.

Download and install a version from

http://hpux.connect.org.uk/hppd/hpux/Gnu/gzip-1.3.5/

Hope this helps,
Robert-Jan

[Leif Halvarsson_2]

Hi,
Which Ignite and HP-UX version do you use ?
I don't think you should need a different version of gzip, I have always used Ingnite with the standard gzip.

Is pax patched.

[Robert-Jan Goossens]

Leif + luke,

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062910172

Regards,
Robert-Jan

[Steven E. Protter · Accepted solution]

Its important to keep track of a couple of things.

1) I've done 20 GB images without updating gzip on 11i. gzip is probably not a factor.

2) You MUST be on the latest version of Ignite 4.30 if you install the pax patch. If not, you will run into a situation where pax can back the files which are bigger than 2 GB but pax_iux on the push/copy side can't unpack it. That issue ate up 6 weeks of my life last year.

3) Since the thing is stopping with no apparent reason, I'd recommend a pax trace on the build. That will give you the error information you need to find out why its stopping.

Here is the pax software:
http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.5/

Here is the code you need to add to the make_sys_image script to do the trace:
TRACE_FILE=/tmp/trace.
pid=$$
TF="${TRACE_FILE}.${pid}.dat"
export TF
/usr/contrib/bin/tusc -f -o $TF -p $pid &

Its kind of a pain, but so much of what ignite does is in the dark, I think its better to run the trace than it is to guess.

SEP

[Luke Bell]

Thanks for your quick responses.

ok the ignite version is Ignite-UX-11-00 B.3.8.201 on the clients and the are all running 11.0

the ignite server has the following ignites installed.

Ignite-UX-10-20 B.3.8.201 HP-UX Installation Utilities for Installing 10.20 Systems
Ignite-UX-11-00 B.3.8.201 HP-UX Installation Utilities for Installing 11.00 Systems
Ignite-UX-11-11 B.3.8.201 HP-UX Installation Utilities for Installing 11.11 Systems

the ignite server is running on 10.20.

Obviously from what Steven has said this will need to be updated.

Robert - I was under the impression that by running a make_sys_image to a directory where the image was more then 2GB is showed that gzip could handle large files?

I suppose the first action is to upgrade ignite on the servers before trying the pax trace.

unless anyone else has any gems.

thanks

Luke

ps i will allocate points when i know if the solutions work.

[Steven E. Protter]

I would now advise the following:

If possible, upgrade Ignite to 4.30 and then install the pax patch.

On that version, don't install the pax patch that allows files bigger than 2 GB because that problem i mentioned in my first post will happen.

The ignite image unpack will just hang and without tusc you'll never be able to figure out why.

SEP

[Bernhard Mueller]

Luke,

verify that the filesystem where your image is to go supports largefiles:

fsadm -F vxfs

Regards,
Bernhard

[Luke Bell]

Bernhard

The file system does support large files the output is shown:

nomultifsets
largefiles

Thanks

Luke

[T G Manikandan]

It gives I/O error which should definitely point to

1.Filesystem space or hard disk problems.
(check /var/adm/syslog/syslog.log)
2.Large file capability by the OS as well as gzip

Just do a which gzip.
gzip <1.2.4a do not support files > 2GB.

[T G Manikandan]

Also,keep an eye on the NFS version used.IT should be nfsv3.

Also keep a note on ULIMIT

[Luke Bell]

Hi TG

ok the syslogs are clear of any errors on the servers that are failing or the ignite server.

I will upgrade my gzip version after I ve finished the upgrade of the ignite software.

I was going to have to upgrade this anyway as we have new servers running a newer version of ignite.

I will then look to upgrade gzip

with the ulimit its set to unlimited on the client but set to 4194303 i will look into this setting more but this should be ok.

[T G Manikandan]

what is the output of

#gzip -V
#which gzip

[T G Manikandan]

Also make sure the archive //(source & destination)// file system are enabled with large files.

[Cheryl Griffin]

Luke,
This does not look like an actual gzip problem.
This could be an NFS filesystem issue. make_sys_image is unable to actually do the writing of the archive due to an NFS issue.
What is this client (model/os)?
With what access/permissions was the filesystem exported?

[Luke Bell]

Cheryl

i would be surprised also if its a gzip issue as i can gzip the fille locally.

The client is a rp5470 running hpux 11.00

The filesystem was exported on the ignite server with read/write access for the client system only.

This is the same for all the systems backing up to the ignite server (30 servers) I only have this problem on three though,

I am thinking it could be an nfs issue as when i do a dmesg on one of the clients i get the following errors (helcis is the ignite server)

NFS server helcis not responding still trying
NFS server helcis ok
NFS server helcis not responding still trying
NFS server helcis ok
NFS server helcis not responding still trying
NFS server helcis ok
WARNING: nfs3write: server wrote 139264, requested was 8192
NFS server helcis not responding still trying
NFS server helcis ok
WARNING: nfs3write: server wrote 139264, requested was 8192

[Luke Bell]

Ive now upgrade to the latest version of ignite 5.1.33 and it all seems to work, ill have to see if those nfs issue are actually issues.

thanks for your help.

[Meir Dukhan]

Hi Luke,

Could you please tell me where did you get Ignite version 5.1.33 ?
What I can see from http://www.software.hp.com/products/IUX/download.html is only the 4.4.30 version.

Thanks,

-- Meir

[Cheryl Griffin]

It is on the application disks.

[Meir Dukhan]

Thanks a lot Cherryl,

Following is a summary of my experiences and also my conclusions.

My ignite server and clients are all 11.0.
In short, I get it work only when I allow Largefiles on the exported filesystem by the Ignite server.
I test this on clients with/without:
. Pax patch (PHCO_25418)
. gzip >= 2 GB files

My conclusion is that only enabling largefiles on the filesystem solved the problem.

ps: I am a newbye to ITRC, would one of you tell me how to assign points ?

Thanks,

-- Meir