|
|
| (3 intermediate revisions by the same user not shown) |
| Line 3: |
Line 3: |
|
| |
|
| <!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all features in the same namespace --> | | <!-- The actual name of your feature page should look something like: Features/YourFeatureName. This keeps all features in the same namespace --> |
|
| |
| = New mkdumprd for kdump <!-- The name of your feature --> =
| |
|
| |
| == Summary ==
| |
| This is a replacement for mkdumprd of kexec-tools, to switch to dracut to generate the initrd for kdump kernel.
| |
|
| |
| == Owner ==
| |
| * Name: [[User:wangcong| Cong Wang]]
| |
|
| |
| <!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved-->
| |
| * Email: <amwang at redhat dot com>
| |
|
| |
| == Current status ==
| |
| * Targeted release: [[Releases/16 | Fedora 16 ]]
| |
| * Last updated: 2011-07-11
| |
| * Percentage of completion: 10%
| |
| Working:
| |
| * Dump to local filesystem
| |
| TODO:
| |
| * Read /etc/kdump.conf to generate initrd
| |
| * Dump to remote host via ssh
| |
| * Dump to remote host via nfs
| |
| * Dump to raw block device
| |
| * Implement full functionality of /etc/kdump.conf
| |
| * Dump to multiple targets
| |
|
| |
| <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
| |
|
| |
| == Detailed Description ==
| |
| Currently in kexec-tools we use our own /sbin/mkdumprd to generate an initrd for kdump kernel. However, due to the natural complexity of making a new initrd, we have lots of burdens to maintain the mkdumprd code, we decide to switch to using dracut to generate kdump initrd. And hopefully, we can provide a distro-independent mkdumprd to upstream, as dracut itself is cross-distribution.
| |
|
| |
| == Benefit to Fedora ==
| |
| The main source of kexec-tools bugs is in mkdumprd, with this change, hopefully we will reduce the number of bugs of kexec-tools.
| |
|
| |
| == Scope ==
| |
| All functionality of /sbin/mkdumprd has to be implemented and tested in this new mkdumprd.
| |
|
| |
| == How To Test ==
| |
| Enable the following config lines in /etc/kdump.conf
| |
| * Dump to local file system
| |
| ext3 LABEL=/boot
| |
| ext3 /dev/sda1
| |
| ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
| |
|
| |
| * Dump to remote machines
| |
| net my.server.com:/path
| |
| net user@remote.server.com
| |
|
| |
| * Dump to raw block device
| |
| raw /dev/sda5
| |
|
| |
| * Other configs
| |
| core_collector makedumpfile -c --message-level 1
| |
| core_collector cp
| |
| kdump_post /var/crash/scripts/kdump-post.sh
| |
| extra_bins /bin/cp
| |
| disk_timeout 30
| |
| extra_modules gfs2
| |
| options modulename options
| |
| default shell
| |
|
| |
| Trigger a crash and see if the vmcore is dumped to the right place.
| |
|
| |
| <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
| |
|
| |
| Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
| |
|
| |
| A good "how to test" should answer these four questions:
| |
|
| |
| 0. What special hardware / data / etc. is needed (if any)?
| |
| 1. How do I prepare my system to test this feature? What packages
| |
| need to be installed, config files edited, etc.?
| |
| 2. What specific actions do I perform to check that the feature is
| |
| working like it's supposed to?
| |
| 3. What are the expected results of those actions?
| |
| -->
| |
|
| |
| == User Experience ==
| |
| Users should not notice the replacement, because we plan to provide full backward compatibility.
| |
|
| |
| == Dependencies ==
| |
| Dracut
| |
|
| |
| == Contingency Plan ==
| |
| Fallback to old /sbin/mkdumprd.
| |
|
| |
| == Documentation ==
| |
| * Not applicable, because we don't need to make documentations for this transparent replacement.
| |
|
| |
| == Release Notes ==
| |
| <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
| |
| <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
| |
| *
| |
|
| |
|
| == Comments and Discussion == | | == Comments and Discussion == |
| * Not applicable, because the main discussion is in a Red Hat internal mailing list. | | * Comments and discussion are welcome! |
| | |
| | |
| [[Category:FeaturePageIncomplete]]
| |
| <!-- When your feature page is completed and ready for review -->
| |
| <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
| |
| <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
| |
| <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
| |
