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