On Tue, Jul 17, 2007 at 03:08:44PM +1000, James C. McPherson wrote:
> >>Log a new case with Sun, and make sure you supply
> >>a crash dump so people who know ZFS can analyze
> >>the issue.
> >>
> >>You can use <stop-A> sync, <break> sync, or
> >>
> >>reboot -dq
> >>
That does appear to have caused a panic/kernel dump. However, I cannot
find the dump image after rebooting to Solaris even thought savecore
appears to be configured,
# reboot -dq
Jul 17 12:27:35 x4500gc reboot: rebooted by root
panic[cpu2]/thread=ffffffff9823c460: forced crash dump initiated at user request
fffffe8000e18d60 genunix:kadmin+4b4 ()
fffffe8000e18ec0 genunix:uadmin+93 ()
fffffe8000e18f10 unix:sys_syscall32+101 ()
syncing file systems... 1 1 done
dumping to /dev/md/dsk/d2, offset 3436511232, content: kernel
100% done: 3268790 pages dumped, compression ratio 12.39, dump succeeded
rebooting...
# dumpadm
Dump content: kernel pages
Dump device: /dev/md/dsk/d2 (swap)
Savecore directory: /var/crash/x4500gc
Savecore enabled: yes
# ls -laR /var/crash/x4500gc/
/var/crash/x4500gc/:
total 2
drwx------ 2 root root 512 Jul 12 16:26 .
drwxr-xr-x 3 root root 512 Jul 12 16:26 ..
Thanks.
--
Stuart Anderson [EMAIL PROTECTED]
http://www.ligo.caltech.edu/~anderson
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
