Re: AIX 52ML04 mksysb questions
Hajo Ehlers wrote:
>
> So depending on your tape drive any value except 0 is a good starting
> point. I would test a value of 1024 and 10240
>
> $ lsattr rmt0 -a block_size # get current value
> $ chdev -l rmt0 -a block_size=10240
> $ mksysb ...
> $ chdev -l rm -a block_size=OldValue
>
Thanks for the tip, and the link. I updgraded the server to 5200-09-CSP
(thatks SOOO much for the pointers; hell, handholding is a better
word!). Following the upgrade, I implemneted your suggestion and it ran
much quicker, although there was a real quirk after I upgraded. I'll
save that for another post; I'd be interested to see what you make odf
it, as I could find NOTHING on the web. Maybe the answer lies in the
link you provided. At anyrate, here's the result of the successful
mksysb. OPne error message that I don't think is anything to worry
about:
# mksysb -m -e /dev/rmt0
Creating information file (/image.data) for rootvg..
Creating tape boot image.................
bosboot: Boot image is 27546 512 byte blocks.
***** ATTENTION *****
The boot image you just created might fail to boot because
the size exceeds the system limit. For information about
fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
***** ATTENTION *****
.....
Creating list of files to back up.
Backing up 65833 files..............................
257 of 65833 files (0%)..............................
748 of 65833 files (1%)........backup: 0511-449 An error occurred
accessing ./tm
p/man585842: A file or directory in the path name does not exist.
.......................
13995 of 65833 files (21%)..............................
25502 of 65833 files (38%)..............................
43125 of 65833 files (65%)..............................
62708 of 65833 files (95%).......
0512-003 mksysb may not have been able to archive some files.
The messages displayed on the Standard Error contained additional
information.
bosboot: Boot image is 27546 512 byte blocks.
***** ATTENTION *****
The boot image you just created might fail to boot because
the size exceeds the system limit. For information about
fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
***** ATTENTION *****
#
Thank you again!
Joe D. |