From: Wiest, Damian (dmwiest@rc2corp.com)
Date: Mon Oct 31 2005 - 15:07:45 EST
Greetings all,
I've run into a strange error with savecore after an E-250 running Solaris 7
crashed; savecore tried to use the wrong dump device.
Here are the entries written to /var/adm/messages:
Oct 28 06:55:30 app01 unix: WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Oct 28 06:55:30 app01 offline
Oct 28 06:55:30 app01 savecore: open("/dev/dsk/c0t0d0s3"): I/O error
Here's the output from dumpadm:
Dump content: kernel pages
Dump device: /dev/md/dsk/d3 (swap)
Savecore directory: /var/crash/app01
Savecore enabled: yes
...and the relevant output from metastat:
d3: Mirror
Submirror 0: d13
State: Okay
Submirror 1: d23
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4198392 blocks
d13: Submirror of d3
State: Okay
Size: 4198392 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c0t9d0s3 0 No Okay
d23: Submirror of d3
State: Okay
Size: 4198392 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s3 0 No Okay
As you can see from the metastat output, d3 does not have any sub-mirrors
that correspond to slot 0 in the E-250's chassis. It _used_ to have a
sub-mirror in slot 0, but that drive failed a couple of weeks ago and I
ended up recreating the sub-mirror in a different location. Why would
savecore try to use the old location?
TIA!
-Damian
_______________________________________________
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:34:10 EDT