Project

General

Profile

Bug #9409

Crash dumps cannot be saved when RAM disks are enabled for /var

Added by Jim Pingle 7 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Operating System
Target version:
Start date:
03/18/2019
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:
All

Description

When a system has RAM disks enabled for /var, the /var/crash directory is missing at bootup when the OS attempts to save crash dumps. As such, the dumps cannot be saved.

Associated revisions

Revision b39d6153 (diff)
Added by Jim Pingle 7 months ago

Create /var/crash after creating /var RAM disk. Fixes #9409

Revision e788a9e2 (diff)
Added by Jim Pingle 7 months ago

Create /var/crash after creating /var RAM disk. Fixes #9409

(cherry picked from commit b39d615394eabd2d19afef0936219c609ef602e3)

History

#1 Updated by Jim Pingle 7 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#2 Updated by Jim Pingle 5 months ago

  • Target version changed from 2.5.0 to 2.4.4-p3

#3 Updated by Constantine Kormashev 5 months ago

Tried on 2.4.4-p3. Set RAM Disk Size to 100 (enable swap) and perform sysctl debug.kdb.panic=1, /var/crash contains dump:

ls -lh /var/crash/
total 116
-rw-r--r--  1 root  wheel     2B May 14 18:26 bounds
-rw-------  1 root  wheel   519B May 14 18:26 info.0
lrwxr-xr-x  1 root  wheel     6B May 14 18:26 info.last -> info.0
-rw-------  1 root  wheel   105K May 14 18:26 textdump.tar.0
lrwxr-xr-x  1 root  wheel    14B May 14 18:26 textdump.tar.last -> textdump.tar.0

#4 Updated by Jim Pingle 5 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF