Bug 1101847 - Add LVM Support to kdump
Summary: Add LVM Support to kdump
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kexec-tools
Version: rawhide
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Baoquan He
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-28 04:50 UTC by Joseph D. Wagner
Modified: 2014-05-29 05:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-29 05:41:12 UTC
Type: Bug


Attachments (Terms of Use)

Description Joseph D. Wagner 2014-05-28 04:50:37 UTC
The default installation uses LVM.  However, kdump does not support LVM, meaning that kdump does not support the default installation.  I do not believe this is an acceptable combination of defaults and features.  (This is particularly problematic if the cause of the kernel crash is located in the storage subsystem.)

Let me give you the example of a small business customer who is paying for support.  They start to experience intermittent kernel dumps.  The fastest way to approach this would be to reconfigure the server to collect dumps which could be sent to the support teams.  However, they cannot because they followed the default installation which uses LVM; a small business could find it difficult and time-consuming to repurpose a spare computer as a netdump server (they might not have a spare); and a small business may have a relatively slow internet connection, like ISDN or a slow DSL/Cable, making online/live/cloud solutions impractical.

I believe making kdump work out-of-the-box with the default configuration will have benefits for developers and their support teams, as well as small business customers who need rapid, low-intervention solutions.

Thank you for your consideration.

Comment 1 WANG Chao 2014-05-28 08:06:48 UTC
How is LVM dump target not working for you? Can you give us an example?

Comment 2 Joseph D. Wagner 2014-05-29 05:41:12 UTC
It must have been a configuration issue.  It works for me now.  Sorry about that.


Note You need to log in before you can comment on or make changes to this bug.