Home > An Internal > An Internal Packing Error Occurred

An Internal Packing Error Occurred

DeleteReplyMuhammad SohailAugust 13, 2013 at 1:23 AMHi, I created a mksysb and spot from it, when tried to restore the image got LED 608. Run lsnim -a locked to see which NIM object has the locks. What OS are you running? Can we replace these files or delete, if non-essential? his comment is here

Blog Articles AIX Maintenance Strategies, Part II AIX allows Priviledge Elevation AIX Maintenance Strategies, Part IV Companies Vision Solutions Toolbox for IT My Home Topics People Companies Jobs White Paper Library Home | Invite Peers | More UNIX Groups Your account is ready. Thank you.ReplyDeleteRepliesaixAugust 13, 2013 at 8:57 AMHi, I think it is not possible....you can extract files from mksysb but I don't know any methods of loading those back. Hope this helps.DeleteBalaJuly 11, 2013 at 2:09 PMi tried it ...actually mksysb will not work for file which have running logs ...for example during the time of mksysb /log is keep

Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... Notify me when an APAR for this component changes. But it's UNIX, it should never need a reboot! Cordially, Edward L.

Registration on or use of this site constitutes acceptance of our Privacy Policy. Watson Product Search Search None of the above, continue with my search IV15898: BACKBYNAME PACKING ERRORS MIGHT RETURN 1 INSTEAD OF 2 APPLIES TO AIX 6100-07 AIX bos.rte.archive. A fix is What is your purpose with that? DeBuhr Senior Technician, Datatrend Technologies, Inc.

Simon Waters replied Nov 27, 2002 Hi UNIX guys, We are still having problems with mksysb: Here's what we have tried: 1.) With mysysb -miX /dev/rt0 command: at 32,779 or 63,134 Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility United States English English IBM® Site map IBM IBM Support Check here to i am trying to take rootvg backup in my testing environment not on a tape drive but on a file in hdisk. http://www.ibm.com/support/docview.wss?uid=isg1IV15898 Creating list of files to back up Backing up 89961 files......................An internal packing error occurred: incorrect size ./var/adm/wtmp will not be backed up. 0512-005 mksysb: Backup Completed.

Can you suggest how to check the consistency of the mksysb backup after completing the backup, means whether the image is restorable or not??Can you please suggest.Thanks.ReplyDeleteRepliesaixMay 11, 2013 at 8:58 For example, related to the error above, you may exclude already /var/adm/wtmp. Unknown User replied Nov 25, 2002 Hello there, I ADMIT it sounds weird, but I got theese symptoms when tried to install with a CD of one version, when the mksysb Software disk reallocation achieved.

In my case mksysb creation has been halted abruptly, and after I killed the stucked mksysb processes the lock was cleared automatically and I was able to do a new mksysb. Simon Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... Register now while it's still free! If you added somme new filesystems to the system, but image.data has not been updated, then it has no knowledge of the added filesystems.

Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... http://crearesiteweb.net/an-internal/an-internal-error-occured.html Error description With IZ85913 installed backbyname will return 1 if a packing error occurred because there is not enough space to copy the file in /tmp or $TMPDIR when the file for example: ^./tmp/ it will backup /tmp, but not the content of it (at restore an empty /tmp will be created) (exclude the contents of /tmp and avoid excluding Savevg backup Unknown asked Mar 29, 2005 | Replies (1) I am trying to run backup for a volume group with savevg and here is the message I get on AIX:

You can add also /tmp or any other temporary files/directories, to avoid other similar errors. # mksysb -eiX /backups-tmp/gzlpar-rootvg.sysb Creating information file (/image.data) for rootvg. renamig the image to a more meaningful name and copying it to the VIOS virtual media library root@bb_lpar: /bb/image # mv cd_image_8323206 bb_lpar_mksysb.iso root@bb_lpar: /bb/image # scp bb_lpar_mksysb.iso aix-vios1:/var/vio/VMLibrary 5. (creating But the mksysb script wiil set rc=0 in done_backup in that case. http://crearesiteweb.net/an-internal/an-internal-error-occurred-while-showing-an-internal-error.html Click Here to join Tek-Tips and talk with other members!

checking the size of an mksysb before creating it: nim -o define -t mksysb -a server=master -a source=LPAR5 -a size_preview=yes -a mk_image=yes -a location=/nim/mksysb.lpar5 mksysb_lpar5 ------------------ mkszfile and image.data: The image.data instead create a large enabled journal filesystem and type is jfs2 .. Printer log tar There is an input or output error.

Creating list of files to back up.

Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. Unless you are referring to something else? If you want to use this information on your own website, please remember: by doing copy/paste entirely it is always stealing and you should be ashamed of yourself! Remove lock in /var/adm/nim and run /usr/lpp/bos.sysmgt/nim/methods/m_chattr -a locked="" to clean up the NIM db entry." ------------------ 0042-207 m_mkbosi: Unable to allocate the exclude_nim resource to machine Always check

create an mksysb (and use the updated image.data) root@bb_lpar: / # mksysb /bb/bb_lpar.mksysb Creating list of files to back up. Return code: -1bosboot error: unable to identify boot diskgetconf: bootinfo replacementmksysb: An internal packing error occurred: incorrect sizetar: 0511-825 The file is too large.NIM (Network Installation Management)Virtual I/O (VIO)Apple WorldCreate bootable MSA ! check over here It disables automatic compression.

This flag only applies to AIX Version 4.2 or later. Simon Waters replied Nov 25, 2002 Hi UNIX-AIX-L support group, I ran the mksysb -p command and about 47% through, I get: 0511-076 Cannot read these specified files: ./usr/lpp/11/include/x11/bitmaps/vsm/com_cum.s.pm " /noteicon.pm ror contained additional"But the status is OK, means these are any warnig message.Shall I use this mksysb backup image to restore the O.S. VSCSI VSCSI - Stor.

the following extracted SPOT is associated...."So, i can't create my new MKSYSB.Can i detach my SPOT from my MKSYSB ? To avoid this kind of problems you can add to /etc/exclude.rootvg the /tmp, /var/tmp,/var/spool/lpd/qdir ----Mensaje original---- De: email@removed Fecha: 06/07/2011 10:34 Para: "mabeleira" Asunto: RE:[ibm-aix-l] mksysb errors Toolbox ibm-aix-l Posted by Notify me when this APAR changes. ISD Basics RMC NETWORKS Basics - Dev., Route Basics - Prot., Subnet Basics - VLAN Commands DSH - PSSH Eth.

Other solution is if you set which customization script to run after restore.DeleteReplyratnakarreddyAugust 20, 2013 at 6:21 PMHi, Thank You for your detailed explanation.I have one question regarding mksysb, when i Problem conclusion we need to change exit value based on the error. Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. IBM: AIX Forum

We are not having much luck here! You can track this item individually or track all items by product. After about 98% complete I recieve the following persistent error: > > "511-084 An internal packing error occurred: incorrect size". > > The mksysb command format I use is: > > as it is recommended by IBM for files/images which are more than 2GB of size.

Verifying command parameters... NO? Or at least link back to this website. nstarkey replied Nov 25, 2002 Earlier, someone mentioned running the 'error report' command.

APAR status Closed as program error. Label: DISK_ERR4 on wra1_boot. exclude files using mksysb -e option and /etc/exclude.rootvg but then these files won't be archived.