Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

aix5.2 ml04 mksysb problem

Status
Not open for further replies.

regatta

MIS
Nov 5, 2004
8
CA
Hi everyone,

I try to backup rootvg using mksysb(aix5.2 ml04),
got attention. the boot image you just created might fail to boot because thesize execeeds the system limit.
How to solve it?
Thanks

 
Are you sending the mksysb to tape or a filesystem? If you are sending it to a filesystem that is a plain JFS filesystem (that is not large file enabled), it sounds as if you are running into the mksysb file being more than 2 GB. Either rebuild your filesystem as a JFS2 filesystem or rebuild it as a JFS filesystem that is large file enabled.

You can tell if the filesystem is large file enabled by doing an lsfs -q /filesystem. If you see bf: false, you have a plain JFS filesystem that is not large file enabled.
 
Hi bi,

Thanks yoyr response. I want send to tape,

regards
 
Regatta,

First off, ML04 was plagued with issues so I would recommend getting to at least ML05, but going straight to ML06 is preferable.

There was an issue with AIX where the boot image became too large and systems failed to boot. That is what this warning message indicates. There is a bunch of information on IBM's website regarding this issue, and IIRC the problem was fixed with an APAR at some point and then reintroduced in AIX 5.2 ML05.

So I would recommend that you go to ML06.

But to address your post directly, this is just a warning message. Create the mksys and see if a machine can boot from it. If the machine can boot off the tape then you are fine.


Jim Hirschauer
 
If you are on 5.2 ML3 or higher, mahe sure your syrtem firmware is up to date.
Changes in the way lscfg talks to NVRAM were introduced in ML3 and later that can cause all sorts of problems if the firmware is not up to date.
In ML5 the problems got worse, so before going on make sure it is up to the latest level.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top