1
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

More than 1 year has passed since last update.

VIOS の "The largest dump device is too small." の解消

Posted at

はじめに

VIOS (Virtual I/O Server) の dumpcheck でダンプデバイスが小さいというエラーが出ていることを解消したログです。
(AIX でもデフォルトでのインストールで同様にエラーがよく出ます。)

エラー内容

$ errlog
IDENTIFIER TIMESTAMP  T C RESOURCE_NAME  DESCRIPTION
E87EF1BE   0526150023 P O dumpcheck      The largest dump device is too small.
E87EF1BE   0525150023 P O dumpcheck      The largest dump device is too small.
E87EF1BE   0524150023 P O dumpcheck      The largest dump device is too small.
E87EF1BE   0523150023 P O dumpcheck      The largest dump device is too small.
E87EF1BE   0522150023 P O dumpcheck      The largest dump device is too small.
E87EF1BE   0521150023 P O dumpcheck      The largest dump device is too small.

エラー詳細

$ errlog -ls
---------------------------------------------------------------------------
LABEL:          DMPCHK_TOOSMALL
IDENTIFIER:     E87EF1BE

Date/Time:       Fri May 26 15:00:00 JST 2023
Sequence Number: 429
Machine Id:      00F98DB54C00
Node Id:         VIOS2
Class:           O
Type:            PEND
WPAR:            Global
Resource Name:   dumpcheck

Description
The largest dump device is too small.

Probable Causes
Neither dump device is large enough to accommodate a system dump at this time.

        Recommended Actions
        Increase the size of one or both dump devices.

Detail Data
Largest dump device
lg_dumplv
Largest dump device size in kb
     1048576
Current estimated dump size in kb
     1343795
---------------------------------------------------------------------------

毎日15時にcronで稼働する dumpcheck で報告されています。

# crontab -l | grep dumpcheck
0 15 * * *  /usr/lib/ras/dumpcheck >/dev/null 2>&1

環境

VIOS(Virtual I/O Server) 3.1.3.14


解消方法

以下を参照して解消します。

参考:

ダンプデバイスのサイズを確認

$ lsvg -lv rootvg | grep sysdump
lg_dumplv           sysdump    16      16      1    open/syncd    N/A
$

-> 16LPs です。

$ lslv lg_dumplv
LOGICAL VOLUME:     lg_dumplv              VOLUME GROUP:   rootvg
LV IDENTIFIER:      00f98db500004c000000017de39824c2.12 PERMISSION:     read/write
VG STATE:           active/complete        LV STATE:       opened/syncd
TYPE:               sysdump                WRITE VERIFY:   off
MAX LPs:            32512                  PP SIZE:        64 megabyte(s)
COPIES:             1                      SCHED POLICY:   parallel
LPs:                16                     PPs:            16
STALE PPs:          0                      BB POLICY:      non-relocatable
INTER-POLICY:       minimum                RELOCATABLE:    yes
INTRA-POLICY:       middle                 UPPER BOUND:    32
MOUNT POINT:        N/A                    LABEL:          None
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?:     NO
INFINITE RETRY:     no                     PREFERRED READ: 0
ENCRYPTION:         no
$

PP SIZE は 64 MB です。

つまりダンプデバイスの "lg_dumplv" は 16 (LPs) x 64 (MB) = 1024 MB です。

ダンプデバイスの見積もりを実施。

# sysdumpdev -e
0453-041 Estimated dump size in bytes: 1377891777
#

1377891777 byte -> およそ 1314 MB
1314 / 64 (MB) = 20.53... => 21 LPs 以上あればよさそうです。

キリの良い数字として 24LPs にするため、8 LPs 追加し、ダンプデバイスを拡張します。

$ extendlv lg_dumplv 8
$ echo $?
0
$
$ lsvg -lv rootvg|grep sysdump
lg_dumplv           sysdump    24      24      1    open/syncd    N/A
$

lg_dumplv の LPs が 24 になりました。

これで毎日のダンプチェックで errlog に出力されなくなりました。

以上です。

1
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
1
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?