Hide Forgot
Description of problem: - When the kdump service starts after a crash, it copies /proc/vmcore to $coredir/vmcore-incomplete - Nothing is showed on the screen until the service is done - We could show the progress Version-Release number of selected component (if applicable): Any How reproducible: 100% Steps to Reproduce: 1. Setup kdump 2. SysRq-c 3. Observe the console output Actual results: Nothing when the kdump service is doing its thing, which can take hours (if one has a lot of RAM) Expected results: Progress indication Additional info: Hopefully replacing in /etc/rc.d/init.d/kdump: cp --sparse=always /proc/vmcore $coredir/vmcore-incomplete with: rsync --verbose --progress --sparse /proc/vmcore $coredir/vmcore-incomplete could be enough. Of course that'd be a new dependency, but we could fallback to cp if rsync is not available.
we normally do show a progress indicator. What does your kdump.conf look like?
This one should be fixed by, https://bugzilla.redhat.com/show_bug.cgi?id=604055 once we start to forward-port those patches to Fedora which will be using makedumpfile by default.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
We will rewrite mkdumprd in Fedora 16 (rawhide), so this BZ doesn't apply any more and can be closed.