xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-06-12 00:00:12 +00:00
Code Issues Releases Wiki Activity

enhance kdump doc crashkernelsize section (#4846)

Browse Source
This commit is contained in:
Yuan Bai
2018-02-27 13:28:58 +08:00
committed by yangsong
parent 029cb0a27c
commit a641e78f73
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/source/guides/admin-guides/manage_clusters/common/deployment/enable_kdump.rst
View File

@ -108,7 +108,7 @@ For system x machine, on sles10 set the crashkernelsize attribute like this: ::
chdef -t osimage <image name> crashkernelsize=<size>M@16M
On sles11 and rhels6 set the crashkernelsize attribute like this: ::
On sles11, rhels6 and above set the crashkernelsize attribute like this: ::
chdef -t osimage <image name> crashkernelsize=<size>M
@ -118,13 +118,21 @@ Where <size> recommended value is 256. For more information about the size can r
`<http://www.novell.com/support/kb/doc.php?id=3374462>`_.
`<https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-kdump-configuration-cli.html>`_.
`<https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/kernel_crash_dump_guide/sect-kdump-config-cli>`_.
For system p machine, set the crashkernelsize attribute to this: ::
chdef -t osimage <image name> crashkernelsize=<size>@32M
For Power System AC922, set the crashkernelsize attribute to this: ::
chdef -t osimage <image name> crashkernelsize=<size>M
Where <size> recommended value is 256, more information can refer the kdump document for the system x.
**Notes**: The ``crashkernel=`` option can be defined in multiple ways. If it is hard to decide the specific crashkernelsize, auto value can be used, the auto value enables automatic configuration of reserved memory based on the total amount of memory in the system like ``crashkernel=auto``.
When your node starts, and you get a kdump start error like this: ::
Your running kernel is using more than 70% of the amount of space you reserved for kdump, you should consider increasing your crashkernel