Hello Stuart, Looks like crash dumped went ok. Check logs after system booted up again if there's a warning that there's no enough space in /var/crash/x4500gc to save crashdump. When using zfs on a file servers crashdumps usually will be almost of server's memory size...
Eventually just run 'savecore path_to_dir' where path_to_dir is a path to a directory with enough free space. Of course assuming you haven't touch swap device up-to this time. -- Best regards, Robert Milkowski mailto:[EMAIL PROTECTED] http://milek.blogspot.com Tuesday, July 17, 2007, 9:04:55 PM, you wrote: SA> It looks like there is a problem dumping a kernel panic on an X4500. SA> During the self induced panic, there where additional syslog messages SA> that indicate a problem writing to the two disks that make up SA> /dev/md/dsk/d2 in my case. It is as if the SATA controllers are being SA> reset during the crash dump. SA> At any rate I will send this all to Sun support. SA> Thanks. SA> Jul 17 12:27:35 x4500gc unix: [ID 836849 kern.notice] SA> Jul 17 12:27:35 x4500gc ^Mpanic[cpu2]/thread=ffffffff9823c460: SA> Jul 17 12:27:35 x4500gc genunix: [ID 156897 kern.notice] forced SA> crash dump initiated at user request SA> Jul 17 12:27:35 x4500gc unix: [ID 100000 kern.notice] SA> Jul 17 12:27:35 x4500gc genunix: [ID 655072 kern.notice] SA> fffffe8000e18d60 genunix:kadmin+4b4 () SA> Jul 17 12:27:35 x4500gc genunix: [ID 655072 kern.notice] SA> fffffe8000e18ec0 genunix:uadmin+93 () SA> Jul 17 12:27:35 x4500gc genunix: [ID 655072 kern.notice] SA> fffffe8000e18f10 unix:sys_syscall32+101 () SA> Jul 17 12:27:35 x4500gc unix: [ID 100000 kern.notice] SA> Jul 17 12:27:35 x4500gc genunix: [ID 672855 kern.notice] syncing file systems... SA> Jul 17 12:27:35 x4500gc genunix: [ID 733762 kern.notice] 1 SA> Jul 17 12:27:37 x4500gc last message repeated 1 time SA> Jul 17 12:27:38 x4500gc genunix: [ID 904073 kern.notice] done SA> Jul 17 12:27:39 x4500gc genunix: [ID 111219 kern.notice] dumping SA> to /dev/md/dsk/d2, offset 3436511232, content: kernel SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 812950 kern.warning] SA> WARNING: marvell88sx3: error on port 0: SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] device disconnected SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] device connected SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] SError interrupt SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 131198 kern.info] SErrors: SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] Recovered communication error SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] PHY ready change SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] 10-bit to 8-bit decode error SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] Disparity error SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 812950 kern.warning] SA> WARNING: marvell88sx3: error on port 4: SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] device disconnected SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] device connected SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] SError interrupt SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 131198 kern.info] SErrors: SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] Recovered communication error SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] PHY ready change SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] 10-bit to 8-bit decode error SA> Jul 17 12:27:39 x4500gc marvell88sx: [ID 517869 kern.info] Disparity error SA> Jul 17 12:28:39 x4500gc genunix: [ID 409368 kern.notice] ^M100% SA> done: 3268790 pages dumped, compression ratio 12.39, SA> Jul 17 12:28:39 x4500gc genunix: [ID 851671 kern.notice] dump succeeded SA> Jul 17 12:30:38 x4500gc genunix: [ID 540533 kern.notice] ^MSunOS SA> Release 5.10 Version Generic_125101-10 64-bit SA> Jul 17 12:30:38 x4500gc genunix: [ID 943907 kern.notice] SA> Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. SA> On Tue, Jul 17, 2007 at 12:40:16PM -0700, Stuart Anderson wrote: >> 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
