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.man.txt
+++ new/usr/src/man/man1m/savecore.1m.man.txt
1 1 SAVECORE(1M) Maintenance Commands SAVECORE(1M)
2 2
3 3
4 4
5 5 NAME
6 6 savecore - save a crash dump of the operating system
7 7
8 8 SYNOPSIS
9 - /usr/bin/savecore [-Lvd] [-f dumpfile] [directory]
9 + /usr/bin/savecore [-L | -r] [-vd] [-f dumpfile] [directory]
10 10
11 11
12 12 DESCRIPTION
13 13 The savecore utility saves a crash dump of the kernel (assuming that
14 14 one was made) and writes a reboot message in the shutdown log. By
15 15 default, it is invoked by the dumpadm service each time the system
16 16 boots.
17 17
18 18
19 19 Depending on the dumpadm(1M) configuration savecore saves either the
20 20 compressed or uncompressed crash dump. The compressed crash dump is
21 21 saved in the file directory/vmdump.n. savecore saves the uncompressed
22 22 crash dump data in the file directory/vmcore.n and the kernel's
23 23 namelist in directory/unix.n. The trailing n in the pathnames is
24 24 replaced by a number which grows every time savecore is run in that
25 25 directory.
26 26
27 27
28 28 Before writing out a crash dump, savecore reads a number from the file
29 29 directory/minfree. This is the minimum number of kilobytes that must
30 30 remain free on the file system containing directory. If after saving
31 31 the crash dump the file system containing directory would have less
32 32 free space the number of kilobytes specified in minfree, the crash dump
33 33 is not saved. if the minfree file does not exist, savecore assumes a
34 34 minfree value of 1 megabyte.
35 35
36 36
37 37 The savecore utility also logs a reboot message using facility LOG_AUTH
38 38 (see syslog(3C)). If the system crashed as a result of a panic,
39 39 savecore logs the panic string too.
40 40
41 41 OPTIONS
42 42 The following options are supported:
43 43
44 44 -d
45 45 Disregard dump header valid flag. Force savecore to
46 46 attempt to save a crash dump even if the header
47 47 information stored on the dump device indicates the dump
48 48 has already been saved.
49 49
50 50
51 51 -f dumpfile
52 52 Attempt to save a crash dump from the specified file
53 53 instead of from the system's current dump device. This
54 54 option may be useful if the information stored on the
55 55 dump device has been copied to an on-disk file by means
56 56 of the dd(1M) command.
57 57
58 58
59 59 -L
60 60 Save a crash dump of the live running Solaris system,
61 61 without actually rebooting or altering the system in any
62 62 way. This option forces savecore to save a live snapshot
63 63 of the system to the dump device, and then immediately
64 64 to retrieve the data and to write it out to a new set of
65 65 crash dump files in the specified directory. Live system
|
↓ open down ↓ |
46 lines elided |
↑ open up ↑ |
66 66 crash dumps can only be performed if you have configured
67 67 your system to have a dedicated dump device using
68 68 dumpadm(1M).
69 69
70 70 savecore -L does not suspend the system, so the contents
71 71 of memory continue to change while the dump is saved.
72 72 This means that live crash dumps are not fully self-
73 73 consistent.
74 74
75 75
76 + -r
77 + Open the dump device or file as read-only, and don't
78 + update the dump header or do anything else that might
79 + modify the crash dump. This option can be used to
80 + recover a crash dump from a read-only device. This flag
81 + cannot be used in conjunction with -L.
82 +
83 +
76 84 -v
77 85 Verbose. Enables verbose error messages from savecore.
78 86
79 87
80 88 OPERANDS
81 89 The following operands are supported:
82 90
83 91 directory
84 92 Save the crash dump files to the specified directory. If
85 93 directory is not specified, savecore saves the crash dump
86 94 files to the default savecore directory, configured by
87 95 dumpadm(1M).
88 96
89 97
90 98 FILES
91 99 directory/vmdump.n
92 100
93 101
94 102
95 103 directory/vmcore.n
96 104
97 105
98 106
99 107 directory/unix.n
100 108
101 109
102 110
103 111 directory/bounds
104 112
105 113
106 114
107 115 directory/minfree
108 116
109 117
110 118
111 119 /var/crash/`uname -n`
112 120 default crash dump directory
113 121
114 122
115 123 SEE ALSO
116 124 adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C),
117 125 attributes(5), smf(5)
118 126
119 127 NOTES
120 128 The system crash dump service is managed by the service management
121 129 facility, smf(5), under the service identifier:
122 130
123 131 svc:/system/dumpadm:default
124 132
125 133
126 134
127 135
128 136 Administrative actions on this service, such as enabling, disabling, or
|
↓ open down ↓ |
43 lines elided |
↑ open up ↑ |
129 137 requesting restart, can be performed using svcadm(1M). The service's
130 138 status can be queried using the svcs(1) command.
131 139
132 140
133 141 If the dump device is also being used as a swap device, you must run
134 142 savecore very soon after booting, before the swap space containing the
135 143 crash dump is overwritten by programs currently running.
136 144
137 145
138 146
139 - January 30, 2013 SAVECORE(1M)
147 + February 22, 2019 SAVECORE(1M)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX