From: Wiest, Damian (dmwiest@rc2corp.com)
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.
-Damian
-----Original Message-----
From: Fernando Boveda [mailto:fernando.boveda@gmail.com]
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,
Fernando
-----Original Message-----
From: John Dewey [mailto:jdewey2@corp.earthlink.net]
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
system
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
dumpfile/20X
dumpfile+10/X
dumpfile+10/s
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.
John
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:35:22 EDT