kdump fails with large ext4 file system because fsck.ext4 gets OOM-killed

Solution Verified - Updated -

Issue

  • kdump fails with large ext4 file system because fsck.ext4 gets OOM-killed
  • We see the following problem when attempting kdump on a 2.1 TB ext4 file system:
/dev/sda4: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Out of memory: Kill process 1014 (fsck.ext4) score 275 or sacrifice child
Killed process 1014, UID 0, (fsck.ext4) total-vm:135812kB, anon-rss:34860kB, file-rss:948kB
KILL
EXT4-fs error (device sda4): ext4_mb_generate_buddy: EXT4-fs: group 24352: 23917 blocks in bitmap, 24544 in gd
  • I see this when kdumping:
Saving to the local filesystem /dev/vdb
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Error allocating block bitmap (1): Memory allocation failed
e2fsck: aborted
EXT4-fs (vdb): mounted filesystem with ordered data mode. Opts:

Environment

  • Red Hat Enterprise Linux (RHEL) 6
  • kdump/kexec
  • ext4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content