RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 857111 - The DUMPFILE field of vmcore showing "vmcore [PARTIAL DUMP]"
Summary: The DUMPFILE field of vmcore showing "vmcore [PARTIAL DUMP]"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: crash
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Dave Anderson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-13 15:20 UTC by Anil
Modified: 2019-09-20 14:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-13 17:28:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Anil 2012-09-13 15:20:37 UTC
Description of problem:

The DUMPFILE field of vmcore showing "vmcore [PARTIAL DUMP]" on RHEL6_U3.

Output from vmcore file
========================

     KERNEL: ../vmlinux                        
    DUMPFILE: vmcore  [PARTIAL DUMP]
        CPUS: 4
        DATE: Thu Sep  6 00:41:02 2012
      UPTIME: 13:53:20
LOAD AVERAGE: 302.68, 302.26, 300.01
       TASKS: 997
    NODENAME: rhel6_u3
     RELEASE: 2.6.32-279.el6.x86_64
     VERSION: #1 SMP Wed Jun 13 18:24:36 EDT 2012
     MACHINE: x86_64  (2000 Mhz)
      MEMORY: 8 GB
       PANIC: "Kernel panic"
         PID: 10536
     COMMAND: "umount"
        TASK: ffff88011e8ff500  [THREAD_INFO: ffff88004681c000]
         CPU: 0
       STATE: TASK_RUNNING (PANIC)


How reproducible:


Steps to Reproduce:
1.generate the vmcore by cmd "echo c > /proc/sysrq-trigger"
2.read this vmcore using crash
3.DUMPFILE field will show "DUMPFILE: vmcore  [PARTIAL DUMP]"

Is the meaning of [PARTIAL DUMP] means we havent got the full dump? can I do my investigation on this dump? 

Also suggest if I miss any setting to take k-dump.

Thanks !!!

Comment 2 Dave Anderson 2012-09-13 17:25:30 UTC
> 1.generate the vmcore by cmd "echo c > /proc/sysrq-trigger"
> 2.read this vmcore using crash
> 3.DUMPFILE field will show "DUMPFILE: vmcore  [PARTIAL DUMP]"
>
> Is the meaning of [PARTIAL DUMP] means we havent got the full dump? 
> can I do my investigation on this dump? 
>
> Also suggest if I miss any setting to take k-dump

The system that crashed has been configured such that the vmcore is
filtered by the makedumpfile facility to remove unnecessary pages.

Check the crashed system's /etc/kdump.conf file.  It probably has a
line that configures "core_collector" to something like this:

 core_collector makedumpfile -c --message-level 1 -d 31

The -c means "compressed" and the "-d <number>" is a bitmask 
that allows you to filter out zero-filled pages, page-cache
pages, user-program pages, and free-pages.  This is the
relevant section from "makedumpfile --help":

[-d DL]:
    Specify the type of unnecessary page for analysis.
    Pages of the specified type are not copied to DUMPFILE. The page type
    marked in the following table is excluded. A user can specify multiple
    page types by setting the sum of each page type for Dump_Level (DL).
    The maximum of Dump_Level is 31.
    Note that Dump_Level for Xen dump filtering is 0 or 1.

     Dump  |  zero   cache   cache    user    free
    Level |  page   page    private  data    page
   -------+---------------------------------------
       0  |
       1  |  X
       2  |         X
       4  |         X       X
       8  |                          X
      16  |                                  X
      31  |  X      X       X        X       X


If your configuration also uses "-c" to make the vmcore file a
compressed dumpfile, you can use the crash utility itself to
access the dump-level value, like this example where -d31 was
used:

crash> help -n | grep dump_level
          dump_level: 31 (0x1f) (DUMP_EXCLUDE_ZERO|DUMP_EXCLUDE_CACHE|DUMP_EXCLUDE_CACHE_PRI|DUMP_EXCLUDE_USER_DATA|DUMP_EXCLUDE_FREE)
crash>

If "-c" was not used, then you would have to consult the /etc/kdump.conf
file on the crashed machine to see how it was configured.

In any case, it's highly unlikely that the contents of any of the 
filterable page-types above are necessary to investigate the cause
of a kernel crash.


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