SUMMARY - Savecore Using Wrong Device

From: Wiest, Damian <>
Date: Tue Nov 08 2005 - 17:54:53 EST
Thanks to Fernando Boveda and John Dewey for their input on this issue.

If you're mirroring the swap device, you need to specify a physical slice
and not a logical device name to the dumpadm(1M) command.

Fernando's and John's responses are listed below.


-----Original Message-----
From: Fernando Boveda [] 
Sent: Monday, October 31, 2005 4:07 PM
To: Wiest, Damian
Subject: Re: Savecore Using Wrong Device

Hi Damian

The problem is that when you configure savecore you must specify the absolut
path to a internal disk drive, if you don't you can fall in the problem you
have now.

When you have Veritas Volume Manager or Solaris Volume Manager ( Disksuite )
you can leave the default , but the things can go wrong as you experienced. 

You must specify the block device path without md or vx ... /dev/dsk/c...  

Then you will have no problem with PANICs.

Best regards,

-----Original Message-----
From: John Dewey [] 
Sent: Monday, October 31, 2005 3:06 PM
To: Wiest, Damian
Subject: Re: Savecore Using Wrong Device

I am not sure why it is not using the correct device.
You must use a special dump device, and not a device that has a file  
on it!

Both the panic() and savecore program need to know the dump device. It looks
like your panic() routine wasn't updated.

To find  your current device:

# adb -k /dev/ksyms /dev/mem

You should see what your dumpfile is.  I am guessing it will report
/dev/dsk/c0t0d0s3 here.

You can then change it in adb session.  There is more information  
about this
on google or the 'Panic!' book.

Use caution when in adb.

sunmanagers mailing list
Received on Tue Nov 8 17:55:17 2005

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:52 EST