search for: savecor

Morning all ... 'K, this one is a first for me ... server crashed this aft and savecore wouldn't dump the resultant core: pluto# savecore -v /vm/crash dumplo = 4362141696 (8519808 * 512) savecore: warning: /kernel version mismatch: "FreeBSD 4.8-STABLE #1: Sat May 31 22:57:04 ADT 2003 " and " #(#(#(" savecore: reboot savecore: dump time is zero...

...I have two servers right now that are updated to recent 4.8-STABLE kernels ... one was June 22nd, and the other was upgraded June 20th ... both of them have crashed since that date, and both of them tell me that they are unable to produce a core file, with the same errors: Jun 26 04:27:14 jupiter savecore: warning: /kernel version mismatch: "FreeBSD 4.8-STABLE #2: Fri Jun 20 18:34:14 ADT 2003 " and "" Prior to those kernel upgrades, I had no problems generating core files, and nothing has changed configuration wise, except as results from upgrading the OS using 'ins...

'k, now one of my other machines is getting the same thing on a crash: savecore: warning: /kernel version mismatch: "FreeBSD 4.8-STABLE #2: Fri Jun 20 18:34:14 ADT 2003 " and "" It was working, last successful savecore on that machine was Jun 6th: -rw------- 1 root wheel 4227792896 Jun 6 23:58 vmcore.1 -rw------- 1 root wheel 4227792896 Ju...

.../dump-file HON hcb116 ~ $ dumpadm -d /var/adm/crash/dump-file dumpadm: dumps not supported on /var/adm/crash/dump-file Using UFS ======== HON hcb115 ~ $ mkfile -n 1g /data/0/test HON hcb115 ~ $ dumpadm -d /data/0/test Dump content: kernel pages Dump device: /data/0/test (dedicated) Savecore directory: /var/crash/stuff Savecore enabled: yes HON hcb115 ~ $

My home NAS box, that I''d upgraded to Solaris 2008.11 after a series of crashes leaving the smf database damaged, and which ran for 4 days cleanly, suddenly fell right back to where the old one had been before. Looking at the logs, I see something similar to (this is manually transcribed to paper and retyped): Bad trap: type=e (page fault) rp=f..f00050e3250 addr=28 module ZFS null

...s > the same each time. It seems that "repairing" corrupted > deduped data by overwriting blocks or whole files with > good copies did not go too well, even though all of my > deduped datasets now use "dedup=verify" mode. > > The uptimes are too short for "savecore" to complete :( > I''ll try to catch the system at a good moment to prevent > "pool"''s importing and hope to get the kernel dump. > > What should I look for with ZDB, MDB or in dump files? > > Any suggestions how to analyze and ultimately fix this...

...755); then on resume, I get a panic. Second problem: When the system panics, I don't get a dump (or textdump for that matter, when I turn them on); in the boot messages, I see "kernel dumps on /dev/ad0s2b" and then later (from memory), "Looking for core dumps on /dev/ad0s2b.... savecore: no dumps found" or somesuch. I know from trying out textdumps that dumping works in other circumstances. These issues together make it hard to debug further, but I did a few tests in single-user mode. First, with no services running, "acpiconf -s3" seems to work OK (although /etc/...

...S) with 500 ntlm_auth subprocesses. Lesser number of ntlm_auth sometimes results in squid crash as it sometimes has several hundreds requests per second to authorize and is intolerant to exhaustion of free ntlm_auth. "squid -k rotatelog" at midnight results in crash: Feb 14 00:03:00 irl savecore: reboot after panic: get_pv_entry: increase vm.pmap.shpgperproc Feb 14 00:03:00 irl savecore: writing core to vmcore.1 Btw, I have coredump. vm.pmap.shpgperproc has default value (200) here, as well as m.v_free_min, vm.v_free_reserved, and vm.v_free_target and KVA_PAGES. These crashes are prett...

...e set up in one big pool with raidz, and it worked great for about a month. On the 4th, we had the system kernel panic and crash, and it''s now behaving very badly. Here''s what diagnostic data I''ve been able to collect so far: In the messages file: Nov 4 13:24:11 mondo4 savecore: [ID 570001 auth.error] reboot after panic: ZFS: I/O failure (write on <unknown> off 0: zio ffffffff97c86a00 [L0 DMU dnode] 4000L/1000P DVA[0]=<0 :d08cf11b800:1800> DVA[1]=<0:1020a711c800:1800> fletcher4 lzjb LE contiguous birth=731555 fill=32 Nov 4 13:24:11 mondo4 savecore: [ID...

...28 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 10.1.2.254 Additional routing options:. Starting devd. Mounting NFS file systems:. Creating and/or trimming log files:. Starting syslogd. Checking for core dump on /dev/ad2s1b... savecore: reboot after panic: page fault Apr 18 18:50:06 cwtest savecore: reboot after panic: page fault savecore: no dump, not enough free space on device (75202 available, need 81542)savecore: unsaved dumps found but not saved Initial i386 initialization:. Additional ABI support: linux/compat/linux/sbin/...

Hi, I may have lost my first zpool, due to ... well, we''re not yet sure. The ''zpool import tank'' causes a panic -- one which I''m not even able to capture via savecore. I''m glad this happened when it did. At home I am in the process of moving all my data from a Linux NFS server to OpenSolaris. It''s something I''d been meaning to do ever since I heard Jeff Bonwick talk about ZFS at LISA ''07. My plan was: - mirrored zfs pool o...

grep union /var/log/messages Jul 2 12:53:01 jupiter savecore: reboot after panic: union_lookup returning . (0xc68e9e90) not same as startdir (0xc5e062c0) Jul 2 14:35:07 jupiter savecore: reboot after panic: union_lookup returning . (0xbf6fee90) not same as startdir (0xbb6d58c0) had two of them today, dumping nice cores ... I'm suspecting its someone t...

The vendor wanted to come in and replace an HDD in the 2nd X4500, as it was "constantly busy", and since our x4500 has always died miserably in the past when a HDD dies, they wanted to replace it before the HDD actually died. The usual was done, HDD replaced, resilvering started and ran for about 50 minutes. Then the system hung, same as always, all ZFS related commands would just

...e. I've made sure my filesystem is clean with fsck and even turned off write caching on my IDE drive. Maybe someone here can figure out what is wrong. Let me know if you need more information. Michael -------------- next part -------------- root@taco /usr/src/sys/compile/ZOE> gdb -k -c /opt/savecore/vmcore.0 /opt/savecore/kernel.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the...

One of our Solaris 10 update 3 servers paniced today with the following error: Sep 18 00:34:53 m2000ef savecore: [ID 570001 auth.error] reboot after panic: assertion failed: ss != NULL, file: ../../common/fs/zfs/space_map.c, line: 125 The server saved a core file, and the resulting backtrace is listed below: $ mdb unix.0 vmcore.0 > $c vpanic() 0xfffffffffb9b49f3() space_map_remove+0x239() space_map_loa...

...;re running SXCE you may need to dedicate a disk or slice for dump purposes. Change or dedicate the dump device with ''dumpadm -d <device>'' See dumpadm(1M) for more info. 2) There are at least a couple of ways to capture crash dumps. As root or with pfexec run ''savecore -L''. This is a point-in-time capture of what''s happening on the live system. The system continues to run during the capture so the results can be slightly inconsistent, but the machine won''t reboot. Good if you think whatever is hung is still making progress. If you...

...-tun 5M /rescue/ping 5M /rescue/reboot 5M /rescue/fastboot 5M /rescue/halt 5M /rescue/fasthalt 5M /rescue/restore 5M /rescue/rrestore 5M /rescue/rcorder 5M /rescue/route 5M /rescue/routed 5M /rescue/rtquery 5M /rescue/rtsol 5M /rescue/savecore 5M /rescue/spppcontrol 5M /rescue/swapon 5M /rescue/sysctl 5M /rescue/tunefs 5M /rescue/umount 5M /rescue/atmconfig 5M /rescue/ping6 5M /rescue/ipf 5M /rescue/zfs 5M /rescue/zpool 5M /rescue/bsdlabel 5M /rescue/disklabel 5M /rescue/f...

A few hours ago I downloaded .../i386/ISO-IMAGES/4.9-RC1-i386-disc1.iso and made kern/mfsroot floppies from it. If I enable my ICH5R SATA controller in "native" mode, the 4.9-RC1 GENERIC kernel hangs solidly (only the system reset button can unwedge it) during device configuration. The last line of bootstrap monologue written by the kernel is: plip0" <PLIP network

We have 10 SuperMicro PDSMi+ 5015M-MTs that are panic'ing every few days. This started shortly after upgrade from 6.2-RELEASE to 6.3-RELEASE with freebsd-update. Other than switching to a debugging kernel, a little sysctl tuning, and patching with freebsd-update, they are stock. The debugging kernel was built from source that is also being patched with freebsd-update. These systems are

...rt 0x2f8-0x2ff irq 3 on isa0 May 14 17:56:43 /kernel: sio1: type 16550A May 14 17:56:43 /kernel: ncp_load: [210-213] May 14 17:56:43 /kernel: ad0: 38166MB <WDC WD400EB-00CPF0> [77545/16/63] at ata0-master UDMA100 May 14 17:56:43 /kernel: Mounting root from ufs:/dev/ad0s1a May 14 17:56:43 savecore: no core dump May 14 17:56:46 /kernel: uhci0: <VIA 83C572 USB controller> port 0xd800-0xd81f irq 12 at device 17.2 on pci0 May 14 17:56:47 /kernel: usb0: <VIA 83C572 USB controller> on uhci0 May 14 17:56:47 /kernel: usb0: USB revision 1.0 May 14 17:56:47 /kernel: uhub0: VIA UHCI ro...