In HP UX :
======
# tusc -afpo
Showing posts with label AIX. Show all posts
Showing posts with label AIX. Show all posts
Wednesday, 23 November 2011
Dump device is too small ? : AIX
- Thanks to Michelle.
1) # /usr/lib/ras/dumpcheck –p
Also you can find the output from # errpt -a
The Output as below:
The largest dump device is too small.
Largest dump device
dumplv01
Largest dump device size in kb
3538944
Current estimated dump size in kb
3561676
Synchronizing
# lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 00cdd76d00004c00000001079dbde229
VG STATE: active PP SIZE: 128 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 2184 (279552 megabytes)
MAX LVs: 256 FREE PPs: 1995 (255360 megabytes)
LVs: 12 USED PPs: 189 (24192 megabytes)
OPEN LVs: 11 QUORUM: 1
TOTAL PVs: 4 VG DESCRIPTORS: 4
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 4 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
FREE PPs shows you have 25GB free on the rootvg and your PP Size is 128mb (IE you can allocate fs extentions in 128mb chunks)
Now show your dump devices :
# sysdumpdev -l
primary /dev/lg_dumplv
secondary /dev/lg_dumplv2
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump TRUE
dump compression OFF
# lslv lg_dumplv
LOGICAL VOLUME: lg_dumplv VOLUME GROUP: rootvg
LV IDENTIFIER: 00cdd76d00004c00000001079dbde229.10 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: sysdump WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 128 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 9 PPs: 8
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL: None
8PPs*128mb*1024 = 1048576 which matches the current size
Calculate the new dump size from the high water mark
1049600/1024/128 = 8.0078125 !!!! Hmmm ok so allocate one more PP just to keep it happy (bad example - I have had to add 12PPs on systems before)
Extent the dumpdev :
# extendlv lg_dumplv 1
# lslv lg_dumplv
LOGICAL VOLUME: lg_dumplv VOLUME GROUP: rootvg
LV IDENTIFIER: 00cdd76d00004c00000001079dbde229.10 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: sysdump WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 128 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 9 PPs: 9
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL:
New size!
Now clear the error
# errclear 0
1) # /usr/lib/ras/dumpcheck –p
Also you can find the output from # errpt -a
The Output as below:
The largest dump device is too small.
Largest dump device
dumplv01
Largest dump device size in kb
3538944
Current estimated dump size in kb
3561676
Synchronizing
# lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 00cdd76d00004c00000001079dbde229
VG STATE: active PP SIZE: 128 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 2184 (279552 megabytes)
MAX LVs: 256 FREE PPs: 1995 (255360 megabytes)
LVs: 12 USED PPs: 189 (24192 megabytes)
OPEN LVs: 11 QUORUM: 1
TOTAL PVs: 4 VG DESCRIPTORS: 4
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 4 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
FREE PPs shows you have 25GB free on the rootvg and your PP Size is 128mb (IE you can allocate fs extentions in 128mb chunks)
Now show your dump devices :
# sysdumpdev -l
primary /dev/lg_dumplv
secondary /dev/lg_dumplv2
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump TRUE
dump compression OFF
# lslv lg_dumplv
LOGICAL VOLUME: lg_dumplv VOLUME GROUP: rootvg
LV IDENTIFIER: 00cdd76d00004c00000001079dbde229.10 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: sysdump WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 128 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 9 PPs: 8
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL: None
8PPs*128mb*1024 = 1048576 which matches the current size
Calculate the new dump size from the high water mark
1049600/1024/128 = 8.0078125 !!!! Hmmm ok so allocate one more PP just to keep it happy (bad example - I have had to add 12PPs on systems before)
Extent the dumpdev :
# extendlv lg_dumplv 1
# lslv lg_dumplv
LOGICAL VOLUME: lg_dumplv VOLUME GROUP: rootvg
LV IDENTIFIER: 00cdd76d00004c00000001079dbde229.10 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: sysdump WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 128 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 9 PPs: 9
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL:
New size!
Now clear the error
# errclear 0
Tuesday, 22 November 2011
SMITTY in AIX
Lot of system admin tasks can be done by using the SMITTY utility in AIX.
Few Examples,
#smit mktcpip # configure network parameters
#smit chfs # change file system, eg grow/extend it.
#smit lsprt # list printers (don't list all, may need to go thru long menu)
#smit installp # Add new software
#smit update # add patches
#smit update_all # automatic add patches to existing sw, no complain if patch is not relevant
smitty fastpath:
Action Prefix Device Abbreviation
------ ------ ------ ------------
(add) mk (printer) prt
(change) ch (tty) tty
(list) ls (pty) pty
(remove) rm (disk) dsk
(cdrom) cdr
(diskette) dskt
(tape) tpe
(adapter) adp
lang
Keystrokes:
F3 or ESC, 3 Cancel, go back
F4 or ESC, 4 Provide list of items to choose from
F6 or ESC, 6 Show command that smit will actually run
F10 or ESC, 10 Exit smitty
Mirror root VG in AIX
Steps to mirror the root VG :
# lspv : determine the hdisk#
# extendvg rootvg hdisk<number> : To add the hdisk to the volume group
# lspv : verify that the hdisk has been successfully added to the volume group
# chvg -Q 'n' rootvg : To change the quorum so that the vg will stay active if one of the mirrors fail
# mirrorvg -S -c 2 rootvg : mirror all of the logical volumes in the volume group
# lsvg -l rootvg : verify successful mirroring (pps will appear "stale" until synchronization is complete).
# bosboot -a -d "disk" : update the boot image information
# bootlist -m normal -o hdisk0 hdisk1 : create a new bootlist
# bootlist -m normal -o : verify the bootlist is correct
# lspv : determine the hdisk#
# extendvg rootvg hdisk<number> : To add the hdisk to the volume group
# lspv : verify that the hdisk has been successfully added to the volume group
# chvg -Q 'n' rootvg : To change the quorum so that the vg will stay active if one of the mirrors fail
# mirrorvg -S -c 2 rootvg : mirror all of the logical volumes in the volume group
# lsvg -l rootvg : verify successful mirroring (pps will appear "stale" until synchronization is complete).
# bosboot -a -d "disk" : update the boot image information
# bootlist -m normal -o hdisk0 hdisk1 : create a new bootlist
# bootlist -m normal -o : verify the bootlist is correct
Subscribe to:
Posts (Atom)