Print this page 
10654 savecore(1M) should be able to work on read-only dump devices
Reviewed by: Robert Mustacchi <rm@joyent.com>
Reviewed by: John Levon <john.levon@joyent.com>
Reviewed by: Andy Stormont <astormont@racktopsystems.com>
Reviewed by: Gergő Doma <domag02@gmail.com>
Reviewed by: Toomas Soome <tsoome@me.com>
Split Close
Expand all
Collapse all
          --- old/usr/src/man/man1m/savecore.1m
          +++ new/usr/src/man/man1m/savecore.1m
   1    1  '\" te
   2    2  .\" Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved.
   3    3  .\" Copyright (c) 1983 Regents of the University of California. All rights reserved. The Berkeley software License Agreement specifies the terms and conditions for redistribution.
   4    4  .\" Copyright 2013 Nexenta Systems, Inc.  All Rights Reserved.
   5      -.TH SAVECORE 1M "Jan 30, 2013"
        5 +.\" Copyright 2019 Joyent, Inc.
        6 +.TH SAVECORE 1M "February 22, 2019"
   6    7  .SH NAME
   7    8  savecore \- save a crash dump of the operating system
   8    9  .SH SYNOPSIS
   9   10  .LP
  10   11  .nf
  11      -\fB/usr/bin/savecore\fR [\fB-Lvd\fR] [\fB-f\fR \fIdumpfile\fR] [\fIdirectory\fR]
       12 +\fB/usr/bin/savecore\fR [\fB-L\fR | \fB-r\fR] [\fB-vd\fR] [\fB-f\fR \fIdumpfile\fR] [\fIdirectory\fR]
  12   13  .fi
  13   14  
  14   15  .SH DESCRIPTION
  15      -.sp
  16   16  .LP
  17   17  The \fBsavecore\fR utility saves a crash dump of the kernel (assuming that one
  18   18  was made) and writes a reboot message in the shutdown log. By default, it is
  19   19  invoked by the \fBdumpadm\fR service each time the system boots.
  20   20  .sp
  21   21  .LP
  22   22  Depending on the \fBdumpadm\fR(1M) configuration \fBsavecore\fR saves either
  23   23  the compressed or uncompressed crash dump. The compressed crash dump is saved in
  24   24  the file \fIdirectory\fR\fB/vmdump.\fR\fIn\fR.
  25   25  \fBsavecore\fR saves the uncompressed crash dump data in the file
↓ open down ↓ 9 lines elided ↑ open up ↑ 
  35   35  the crash dump the file system containing \fIdirectory\fR would have less free
  36   36  space the number of kilobytes specified in \fBminfree\fR, the crash dump is not
  37   37  saved. if the \fBminfree\fR file does not exist, \fBsavecore\fR assumes a
  38   38  \fBminfree\fR value of 1 megabyte.
  39   39  .sp
  40   40  .LP
  41   41  The \fBsavecore\fR utility also logs a reboot message using facility
  42   42  \fBLOG_AUTH\fR (see \fBsyslog\fR(3C)). If the system crashed as a result of a
  43   43  panic, \fBsavecore\fR logs the panic string too.
  44   44  .SH OPTIONS
  45      -.sp
  46   45  .LP
  47   46  The following options are supported:
  48   47  .sp
  49   48  .ne 2
  50   49  .na
  51   50  \fB\fB-d\fR\fR
  52   51  .ad
  53   52  .RS 15n
  54   53  Disregard dump header valid flag. Force \fBsavecore\fR to attempt to save a
  55   54  crash dump even if the header information stored on the dump device indicates
↓ open down ↓ 27 lines elided ↑ open up ↑ 
  83   82  \fBdumpadm\fR(1M).
  84   83  .sp
  85   84  \fBsavecore\fR \fB-L\fR does not suspend the system, so the contents of memory
  86   85  continue to change while the dump is saved. This means that live crash dumps
  87   86  are not fully self-consistent.
  88   87  .RE
  89   88  
  90   89  .sp
  91   90  .ne 2
  92   91  .na
       92 +\fB\fB-r\fR\fR
       93 +.ad
       94 +.RS 15n
       95 +Open the dump device or file as read-only, and don't update the dump header
       96 +or do anything else that might modify the crash dump. This option can be used
       97 +to recover a crash dump from a read-only device. This flag cannot be used in
       98 +conjunction with \fB\fB-L\fR\fR.
       99 +.RE
      100 +
      101 +.sp
      102 +.ne 2
      103 +.na
  93  104  \fB\fB-v\fR\fR
  94  105  .ad
  95  106  .RS 15n
  96  107  Verbose. Enables verbose error messages from \fBsavecore\fR.
  97  108  .RE
  98  109  
  99  110  .SH OPERANDS
 100      -.sp
 101  111  .LP
 102  112  The following operands are supported:
 103  113  .sp
 104  114  .ne 2
 105  115  .na
 106  116  \fB\fIdirectory\fR\fR
 107  117  .ad
 108  118  .RS 13n
 109  119  Save the crash dump files to the specified directory. If \fIdirectory\fR is not
 110  120  specified, \fBsavecore\fR saves the crash dump files to the default
 111  121  \fBsavecore\fR \fIdirectory\fR, configured by \fBdumpadm\fR(1M).
 112  122  .RE
 113  123  
 114  124  .SH FILES
 115      -.sp
 116  125  .ne 2
 117  126  .na
 118  127  \fB\fIdirectory\fR\fB/vmdump.\fR\fIn\fR\fR
 119  128  .ad
 120  129  .RS 29n
 121  130  
 122  131  .RE
 123  132  
 124  133  .sp
 125  134  .ne 2
↓ open down ↓ 34 lines elided ↑ open up ↑ 
 160  169  .sp
 161  170  .ne 2
 162  171  .na
 163  172  \fB\fB/var/crash/\&`uname \fR\fB-n\fR\fB\&`\fR\fR
 164  173  .ad
 165  174  .RS 29n
 166  175  default crash dump directory
 167  176  .RE
 168  177  
 169  178  .SH SEE ALSO
 170      -.sp
 171  179  .LP
 172  180  \fBadb\fR(1), \fBmdb\fR(1), \fBsvcs\fR(1), \fBdd\fR(1M), \fBdumpadm\fR(1M),
 173  181  \fBsvcadm\fR(1M), \fBsyslog\fR(3C), \fBattributes\fR(5), \fBsmf\fR(5)
 174  182  .SH NOTES
 175      -.sp
 176  183  .LP
 177  184  The system crash dump service is managed by the service management facility,
 178  185  \fBsmf\fR(5), under the service identifier:
 179  186  .sp
 180  187  .in +2
 181  188  .nf
 182  189  svc:/system/dumpadm:default
 183  190  .fi
 184  191  .in -2
 185  192  .sp
↓ open down ↓ 11 lines elided ↑ open up ↑ 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX