SYSBACK: /tmp full or hang when editing vginfo
CUSTOMER IS HIGHLY SENSITIVE. PLEASE ASSIST PROPERLY.
Trying to do a recover w/sysback to different
No vg info was found.
He was in the midst of chg'g vg attributes when
he started getting this msg....
Problem restoring with sysback
Customer was trying to restore a R50 on to a J40 - the J40 had
half the disk space and less memory. Old system rootvg was on
2.2G drives - pp 4 - tried to change the pp to 8(new system 4.5G)
other volume group wanted to change pp from 16 to 8. Customer
also wanted to turn mirroring off. Failed when changing attributes
- couldn't change lvminfor - ran out of space. Customer will
reboot from tape and call back to make the changes.
TRANSFERRED SEARCY TO DORIS LIVE
HOW TO INCREASE THE SIZE OF THE RAMFS WITH CHRAMFS
This will work when there is enough space in the filesystem to
get to the main menu, but when you start working with volume
group information you fail with an 'out of space' error:
1. Find a system with the same level of aix, we found a 4.1.4
system and it was OK to use on 4.1.5, but you can't use a 4.2 or 4.3
on 4.1. Put an initialized floppy in the drive.
2. cd /usr/lib/boot
3. chmod 775 chramfs
4. backup -ivqf /dev/fd0 ./chramfs
5. On the system that has the error, reboot and when the Main
menu comes up, pick to go into the maintenance shell. Put the
floppy in the drive.
6. cd /tmp
7. restore -xqf /dev/fd0
8. specify the size to increase the filesystem:
If the size is 16m (16384) and you want to go to 20m (20480),
9. df ----- the size should have changed
10. exit -------- continue normally from here.
Customer called back - same problem. Went from 7135 scsi raid arrays
drives to 7133 scsi ssa drives(about 30 or more). Ram was at
100% used. Customer rebooted, conferenced in JR - checked /dev/ram0
Doris, close this as a library item. Thanks
Support Line: SYSBACK: /tmp full or hang when editing vginfo ITEM: HD9755L
Dated: August 1998 Category: N/A
This HTML file was generated 99/06/24~13:30:13
Comments or suggestions?