Bug 745115

Summary: kdump always dumps the whole memory
Product: [Fedora] Fedora Reporter: Michal Toman <mtoman>
Component: kexec-toolsAssignee: Dave Young <ruyang>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: jmoskovc, nhorman, pknirsch, qcai, rvokal, xiyou.wangcong
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 788999 (view as bug list) Environment:
Last Closed: 2013-02-13 22:14:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 788999    

Description Michal Toman 2011-10-11 12:45:03 UTC
Description of problem:
After executing the crash kernel, kdump seems to ignore the config file (containing "core_collector makedumpfile -c -d 17") and always dumps the whole memory.

Version-Release number of selected component (if applicable):
kernel-3.1.0-0.rc9.git0.0.fc16.x86_64 + kexec-tools-2.0.2-29.fc16.x86_64
kernel-2.6.40.6-0.fc15.x86_64 + kexec-tools-2.0.0-44.fc15.x86_64
kernel-2.6.35.14-97.fc14.x86_64 + kexec-tools-2.0.0-41.fc14.x86_64

How reproducible:
Always
  
Actual results:
All memory is dumped.

Expected results:
Specified pages are excluded from the resulting vmcore.

Additional info:
When looking to process list in the crash kernel, the dumping is realized by simply "cp --sparse=always /proc/vmcore /var/crash/xyz/vmcore". Running makedumpfile "by hand" works as expected.

Comment 1 Américo Wang 2011-11-11 08:28:12 UTC
Hi, Michal,

Your kdump.conf please? If "core_collector" is the only thing you specified in your kdump.conf, then you should see the warning:

Warning!  Lack of dump target specification means core_collector option is ignored!

which means in this case the core_collector is ignored on purpose, not a bug.

Comment 2 Michal Toman 2011-11-11 09:51:17 UTC
I have

path /var/crash
core_collector makedumpfile -c -d 17

This works on el6, but doesn't on Fedora.
I can only see the warning "Warning!  Lack of dump target specification means default option is ignored!" if I set

default shell

Setting core_collector does not seem to issue anything.
Is there anything else I need to set up?

Comment 3 Fedora Admin XMLRPC Client 2012-04-16 06:12:48 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora End Of Life 2013-01-16 17:29:40 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 22:14:12 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.