savecore(1M) may return "bad magic number" after changing ZFS dump device volsize
Last updated on JUNE 12, 2017
Applies to:Solaris Operating System - Version 10 6/06 U2 to 10 1/13 U11 [Release 10.0]
Solaris Operating System - Version 11.1 to 11.2 [Release 11.0]
Information in this document applies to any platform.
If the issue described in this document is encountered, executing savecore may return a message similar to the following
# savecore -vd -D .
savecore: bad magic number cccccccc, savecore: Failed to read valid dump header from dump file /dev/zvol/dsk/rpool/dump
Re-sizing /dev/zvol/dsk/rpool/dump using 'zfs set volsize=newsize rpool/dump'
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms