kdump in CentOS 7
Clash Royale CLAN TAG#URR8PPP
I wanted to migrate to CentOS 7.5 from CentOS 6.9. during installation I saw an option kdump that i could enable or disable. I wonder what is kdump and disabling it has any bad effect on server? I want to install database on my server later I just want to make sure that kdump cause no problem.
centos kernel sqlserver kdump
asked Dec 29 '18 at 6:37
BlackCrystalBlackCrystal
32611
add a comment |
I wanted to migrate to CentOS 7.5 from CentOS 6.9. during installation I saw an option kdump that i could enable or disable. I wonder what is kdump and disabling it has any bad effect on server? I want to install database on my server later I just want to make sure that kdump cause no problem.
centos kernel sqlserver kdump
asked Dec 29 '18 at 6:37
BlackCrystalBlackCrystal
32611
add a comment |
I wanted to migrate to CentOS 7.5 from CentOS 6.9. during installation I saw an option kdump that i could enable or disable. I wonder what is kdump and disabling it has any bad effect on server? I want to install database on my server later I just want to make sure that kdump cause no problem.
centos kernel sqlserver kdump
asked Dec 29 '18 at 6:37
BlackCrystalBlackCrystal
32611
I wanted to migrate to CentOS 7.5 from CentOS 6.9. during installation I saw an option kdump that i could enable or disable. I wonder what is kdump and disabling it has any bad effect on server? I want to install database on my server later I just want to make sure that kdump cause no problem.
centos kernel sqlserver kdump
centos kernel sqlserver kdump
asked Dec 29 '18 at 6:37
BlackCrystalBlackCrystal
32611
asked Dec 29 '18 at 6:37
BlackCrystalBlackCrystal
32611
asked Dec 29 '18 at 6:37
BlackCrystalBlackCrystal
32611
asked Dec 29 '18 at 6:37
BlackCrystalBlackCrystal
32611
asked Dec 29 '18 at 6:37
BlackCrystalBlackCrystal
32611
32611
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
kdump is a kernel crash dumping mechanism. In the event of a system crash, kdump produces a crash dump of the kernel that can be used for further analysis. Depending upon the severity of the failure, this crash dump may be the only information available for further analysis.
In the event of a system crash, kdump works by loading a second kernel into memory using the kexec system call. This second kernel captures the contents of the first kernel's memory. This information is saved as the crash dump.
To allow the second kernel to be loaded into memory, a part of the system memory has to be permanently reserved for it. This area of memory is inaccessible to the first kernel. The amount of memory reserved depends on the system architecture and the total amount of memory installed on the system. As an example, a system with the x86_64 architecture and 2 GiB of installed memory will require a minimum amount of 163968 KiB (160.25 MiB) to be reserved for kdump.
RHEL 7 (and CentOS 7, by extension) have the kdump mechanism installed and activated by default for (most) new installations. The Anaconda installer provides limited options for configuring kdump. Other installation options such as Kickstart may not have kdump enabled by default.
Further details on kdump (installation, configuration, usage) can be found at the RHEL 7 Documentation on Kernel Administration: Kernel Crash Dump Guide
answered Dec 29 '18 at 8:42
HaxielHaxiel
1,552410
add a comment |
kdump dumps the kernel memory in the event of a kernel crash. So
If your kernel never crashes it is safe to disable kdump
If you don't care about a kernel crash it is safe to disable kdump
If you don't have a support contract and don't have the needed knowledge to debug a kernel crash yourself and are unwilling to pay someone on a one off basis to diagnose a kernel crash, it is safe to disable kdump.
Otherwise leave it enabled.
For most people (1) is true. For the rest either (2) or (3) is probably true. If you make a high value device with embedded linux then kdump can be extremely valuable.
answered Dec 29 '18 at 8:49
icarusicarus
5,7411929
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491418%2fkdump-in-centos-7%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
kdump is a kernel crash dumping mechanism. In the event of a system crash, kdump produces a crash dump of the kernel that can be used for further analysis. Depending upon the severity of the failure, this crash dump may be the only information available for further analysis.
In the event of a system crash, kdump works by loading a second kernel into memory using the kexec system call. This second kernel captures the contents of the first kernel's memory. This information is saved as the crash dump.
To allow the second kernel to be loaded into memory, a part of the system memory has to be permanently reserved for it. This area of memory is inaccessible to the first kernel. The amount of memory reserved depends on the system architecture and the total amount of memory installed on the system. As an example, a system with the x86_64 architecture and 2 GiB of installed memory will require a minimum amount of 163968 KiB (160.25 MiB) to be reserved for kdump.
RHEL 7 (and CentOS 7, by extension) have the kdump mechanism installed and activated by default for (most) new installations. The Anaconda installer provides limited options for configuring kdump. Other installation options such as Kickstart may not have kdump enabled by default.
Further details on kdump (installation, configuration, usage) can be found at the RHEL 7 Documentation on Kernel Administration: Kernel Crash Dump Guide
answered Dec 29 '18 at 8:42
HaxielHaxiel
1,552410
add a comment |
kdump is a kernel crash dumping mechanism. In the event of a system crash, kdump produces a crash dump of the kernel that can be used for further analysis. Depending upon the severity of the failure, this crash dump may be the only information available for further analysis.
In the event of a system crash, kdump works by loading a second kernel into memory using the kexec system call. This second kernel captures the contents of the first kernel's memory. This information is saved as the crash dump.
To allow the second kernel to be loaded into memory, a part of the system memory has to be permanently reserved for it. This area of memory is inaccessible to the first kernel. The amount of memory reserved depends on the system architecture and the total amount of memory installed on the system. As an example, a system with the x86_64 architecture and 2 GiB of installed memory will require a minimum amount of 163968 KiB (160.25 MiB) to be reserved for kdump.
RHEL 7 (and CentOS 7, by extension) have the kdump mechanism installed and activated by default for (most) new installations. The Anaconda installer provides limited options for configuring kdump. Other installation options such as Kickstart may not have kdump enabled by default.
Further details on kdump (installation, configuration, usage) can be found at the RHEL 7 Documentation on Kernel Administration: Kernel Crash Dump Guide
answered Dec 29 '18 at 8:42
HaxielHaxiel
1,552410
add a comment |
kdump is a kernel crash dumping mechanism. In the event of a system crash, kdump produces a crash dump of the kernel that can be used for further analysis. Depending upon the severity of the failure, this crash dump may be the only information available for further analysis.
In the event of a system crash, kdump works by loading a second kernel into memory using the kexec system call. This second kernel captures the contents of the first kernel's memory. This information is saved as the crash dump.
To allow the second kernel to be loaded into memory, a part of the system memory has to be permanently reserved for it. This area of memory is inaccessible to the first kernel. The amount of memory reserved depends on the system architecture and the total amount of memory installed on the system. As an example, a system with the x86_64 architecture and 2 GiB of installed memory will require a minimum amount of 163968 KiB (160.25 MiB) to be reserved for kdump.
RHEL 7 (and CentOS 7, by extension) have the kdump mechanism installed and activated by default for (most) new installations. The Anaconda installer provides limited options for configuring kdump. Other installation options such as Kickstart may not have kdump enabled by default.
Further details on kdump (installation, configuration, usage) can be found at the RHEL 7 Documentation on Kernel Administration: Kernel Crash Dump Guide
answered Dec 29 '18 at 8:42
HaxielHaxiel
1,552410
kdump is a kernel crash dumping mechanism. In the event of a system crash, kdump produces a crash dump of the kernel that can be used for further analysis. Depending upon the severity of the failure, this crash dump may be the only information available for further analysis.
In the event of a system crash, kdump works by loading a second kernel into memory using the kexec system call. This second kernel captures the contents of the first kernel's memory. This information is saved as the crash dump.
To allow the second kernel to be loaded into memory, a part of the system memory has to be permanently reserved for it. This area of memory is inaccessible to the first kernel. The amount of memory reserved depends on the system architecture and the total amount of memory installed on the system. As an example, a system with the x86_64 architecture and 2 GiB of installed memory will require a minimum amount of 163968 KiB (160.25 MiB) to be reserved for kdump.
RHEL 7 (and CentOS 7, by extension) have the kdump mechanism installed and activated by default for (most) new installations. The Anaconda installer provides limited options for configuring kdump. Other installation options such as Kickstart may not have kdump enabled by default.
Further details on kdump (installation, configuration, usage) can be found at the RHEL 7 Documentation on Kernel Administration: Kernel Crash Dump Guide
answered Dec 29 '18 at 8:42
HaxielHaxiel
1,552410
answered Dec 29 '18 at 8:42
HaxielHaxiel
1,552410
answered Dec 29 '18 at 8:42
HaxielHaxiel
1,552410
answered Dec 29 '18 at 8:42
HaxielHaxiel
1,552410
1,552410
add a comment |
add a comment |
kdump dumps the kernel memory in the event of a kernel crash. So
If your kernel never crashes it is safe to disable kdump
If you don't care about a kernel crash it is safe to disable kdump
If you don't have a support contract and don't have the needed knowledge to debug a kernel crash yourself and are unwilling to pay someone on a one off basis to diagnose a kernel crash, it is safe to disable kdump.
Otherwise leave it enabled.
For most people (1) is true. For the rest either (2) or (3) is probably true. If you make a high value device with embedded linux then kdump can be extremely valuable.
answered Dec 29 '18 at 8:49
icarusicarus
5,7411929
add a comment |
kdump dumps the kernel memory in the event of a kernel crash. So
If your kernel never crashes it is safe to disable kdump
If you don't care about a kernel crash it is safe to disable kdump
If you don't have a support contract and don't have the needed knowledge to debug a kernel crash yourself and are unwilling to pay someone on a one off basis to diagnose a kernel crash, it is safe to disable kdump.
Otherwise leave it enabled.
For most people (1) is true. For the rest either (2) or (3) is probably true. If you make a high value device with embedded linux then kdump can be extremely valuable.
answered Dec 29 '18 at 8:49
icarusicarus
5,7411929
add a comment |
kdump dumps the kernel memory in the event of a kernel crash. So
If your kernel never crashes it is safe to disable kdump
If you don't care about a kernel crash it is safe to disable kdump
If you don't have a support contract and don't have the needed knowledge to debug a kernel crash yourself and are unwilling to pay someone on a one off basis to diagnose a kernel crash, it is safe to disable kdump.
Otherwise leave it enabled.
For most people (1) is true. For the rest either (2) or (3) is probably true. If you make a high value device with embedded linux then kdump can be extremely valuable.
answered Dec 29 '18 at 8:49
icarusicarus
5,7411929
kdump dumps the kernel memory in the event of a kernel crash. So
If your kernel never crashes it is safe to disable kdump
If you don't care about a kernel crash it is safe to disable kdump
If you don't have a support contract and don't have the needed knowledge to debug a kernel crash yourself and are unwilling to pay someone on a one off basis to diagnose a kernel crash, it is safe to disable kdump.
Otherwise leave it enabled.
For most people (1) is true. For the rest either (2) or (3) is probably true. If you make a high value device with embedded linux then kdump can be extremely valuable.
answered Dec 29 '18 at 8:49
icarusicarus
5,7411929
answered Dec 29 '18 at 8:49
icarusicarus
5,7411929
answered Dec 29 '18 at 8:49
icarusicarus
5,7411929
answered Dec 29 '18 at 8:49
icarusicarus
5,7411929
5,7411929
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491418%2fkdump-in-centos-7%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown