Re: savecore problem
On Mon, Mar 16, 2015 at 12:06 PM, Michael BlackHeart amdm...@gmail.com wrote: I've tried to run manually savecore. I tried before RAID get OPTIMAL and after that. dumpmon says: dumpon -l raid/r0p3 savecore -vvf /var/crash /dev/raid/r0p3 worked now but... It extracted another dump from october 2014. On my box swap used just a little so I blieve that there might be that dump but where's dump from march,15 2015? I'd like to figure out what happend with savecore and kernel dumps. Is there a safe way to test this functional? Some test kernel panics? sysctl debug.kdb.panic=1 will force an immediate panic. Also, how much space do you have on /dev/raid/r0p3? It's possible that the core is in your swap partition but savecore won't save it because you don't have enough space. savecore tries to calculate the space required, but it overestimates. You can check whether a core exists, without trying to save it, by savecore -C -Alan 2015-03-16 18:33 GMT+03:00 Konstantin Kulikov k.kulik...@gmail.com: Hello, have you tried to run savecore manually, like savecore -vvf /var/crash /dev/raid/r0p3 Also check that your dump device is working (dumpon -l) On Mon, Mar 16, 2015 at 4:40 PM, Michael BlackHeart amdm...@gmail.com wrote: Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash Filesystem is UFS FreeBSD diablo.miekoff.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r277169: Thu Jan 15 10:22:34 MSK 2015 amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 rc.conf configuration dumpdev=AUTO dumpdir=/var/crash/ RAID 1 via graid configuration (JMicron based) graid list Geom name: JMicron-6e1c79e State: OPTIMAL Metadata: JMicron Providers: 1. Name: raid/r0 Mediasize: 120024203264 (112G) Sectorsize: 512 Mode: r6w6e16 Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) Dirty: No State: OPTIMAL Strip: 1024 Components: 2 Transformation: RAID1 RAIDLevel: RAID1 Label: SYSMIRROR descr: JMicron RAID1 volume Consumers: 1. Name: ada0 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):0@0 State: ACTIVE (ACTIVE) 2. Name: ada1 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):1@0 State: ACTIVE (ACTIVE) /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ufs/rootfs / ufs rw,noatime 1 1 /dev/raid/r0p3 noneswapsw 0 0 /dev/ufs/varfs /varufs rw,noatime 2 2 /dev/ufs/tmpfs /tmpufs rw,noatime 2 2 /dev/ufs/usrfs /usrufs rw,noatime 2 2 /dev/ufs/configfs /config ufs rw,noatime 2 2 tmpfs /usr/tmpfs tmpfs rw 0 0 proc/proc procfs rw 0 0 fdesc /dev/fd fdescfs rw 0 0 In kernel configuration DEBUG -g is disabled. -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: savecore problem
On Mon, Mar 16, 2015 at 9:40 AM, Michael BlackHeart amdm...@gmail.com wrote: Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash (...) /dev/ufs/varfs /varufs rw,noatime 2 2 Last I checked, savecore had to happen very early --- before filesystems other than / are mounted. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: savecore problem
On 2015-03-16 11:23, John Baldwin wrote: On Monday, March 16, 2015 10:17:54 AM Brandon Allbery wrote: On Mon, Mar 16, 2015 at 9:40 AM, Michael BlackHeart amdm...@gmail.com wrote: Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash (...) /dev/ufs/varfs /varufs rw,noatime 2 2 Last I checked, savecore had to happen very early --- before filesystems other than / are mounted. No, it can happen after that. What really has to happen is that you don't use swap (if you are dumping to your swap partition) before savecore runs. Can someone elaborate on not using swap as a dump device a little more? I have had instances in the past were I had issues with getting a core dump and resorted to a dedicated dump device but didn't investigate further nor have I read this as a requirement. A second question - Can a USB devices be used reliably for a dump device for ZFS on boot systems? Regards, Michael Jung ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: savecore problem
On Monday, March 16, 2015 10:17:54 AM Brandon Allbery wrote: On Mon, Mar 16, 2015 at 9:40 AM, Michael BlackHeart amdm...@gmail.com wrote: Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash (...) /dev/ufs/varfs /varufs rw,noatime 2 2 Last I checked, savecore had to happen very early --- before filesystems other than / are mounted. No, it can happen after that. What really has to happen is that you don't use swap (if you are dumping to your swap partition) before savecore runs. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: savecore problem
Hello, have you tried to run savecore manually, like savecore -vvf /var/crash /dev/raid/r0p3 Also check that your dump device is working (dumpon -l) On Mon, Mar 16, 2015 at 4:40 PM, Michael BlackHeart amdm...@gmail.com wrote: Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash Filesystem is UFS FreeBSD diablo.miekoff.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r277169: Thu Jan 15 10:22:34 MSK 2015 amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 rc.conf configuration dumpdev=AUTO dumpdir=/var/crash/ RAID 1 via graid configuration (JMicron based) graid list Geom name: JMicron-6e1c79e State: OPTIMAL Metadata: JMicron Providers: 1. Name: raid/r0 Mediasize: 120024203264 (112G) Sectorsize: 512 Mode: r6w6e16 Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) Dirty: No State: OPTIMAL Strip: 1024 Components: 2 Transformation: RAID1 RAIDLevel: RAID1 Label: SYSMIRROR descr: JMicron RAID1 volume Consumers: 1. Name: ada0 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):0@0 State: ACTIVE (ACTIVE) 2. Name: ada1 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):1@0 State: ACTIVE (ACTIVE) /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ufs/rootfs / ufs rw,noatime 1 1 /dev/raid/r0p3 noneswapsw 0 0 /dev/ufs/varfs /varufs rw,noatime 2 2 /dev/ufs/tmpfs /tmpufs rw,noatime 2 2 /dev/ufs/usrfs /usrufs rw,noatime 2 2 /dev/ufs/configfs /config ufs rw,noatime 2 2 tmpfs /usr/tmpfs tmpfs rw 0 0 proc/proc procfs rw 0 0 fdesc /dev/fd fdescfs rw 0 0 In kernel configuration DEBUG -g is disabled. -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: savecore problem
I've tried to run manually savecore. I tried before RAID get OPTIMAL and after that. dumpmon says: dumpon -l raid/r0p3 savecore -vvf /var/crash /dev/raid/r0p3 worked now but... It extracted another dump from october 2014. On my box swap used just a little so I blieve that there might be that dump but where's dump from march,15 2015? I'd like to figure out what happend with savecore and kernel dumps. Is there a safe way to test this functional? Some test kernel panics? 2015-03-16 18:33 GMT+03:00 Konstantin Kulikov k.kulik...@gmail.com: Hello, have you tried to run savecore manually, like savecore -vvf /var/crash /dev/raid/r0p3 Also check that your dump device is working (dumpon -l) On Mon, Mar 16, 2015 at 4:40 PM, Michael BlackHeart amdm...@gmail.com wrote: Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash Filesystem is UFS FreeBSD diablo.miekoff.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r277169: Thu Jan 15 10:22:34 MSK 2015 amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 rc.conf configuration dumpdev=AUTO dumpdir=/var/crash/ RAID 1 via graid configuration (JMicron based) graid list Geom name: JMicron-6e1c79e State: OPTIMAL Metadata: JMicron Providers: 1. Name: raid/r0 Mediasize: 120024203264 (112G) Sectorsize: 512 Mode: r6w6e16 Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) Dirty: No State: OPTIMAL Strip: 1024 Components: 2 Transformation: RAID1 RAIDLevel: RAID1 Label: SYSMIRROR descr: JMicron RAID1 volume Consumers: 1. Name: ada0 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):0@0 State: ACTIVE (ACTIVE) 2. Name: ada1 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):1@0 State: ACTIVE (ACTIVE) /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ufs/rootfs / ufs rw,noatime 1 1 /dev/raid/r0p3 noneswapsw 0 0 /dev/ufs/varfs /varufs rw,noatime 2 2 /dev/ufs/tmpfs /tmpufs rw,noatime 2 2 /dev/ufs/usrfs /usrufs rw,noatime 2 2 /dev/ufs/configfs /config ufs rw,noatime 2 2 tmpfs /usr/tmpfs tmpfs rw 0 0 proc/proc procfs rw 0 0 fdesc /dev/fd fdescfs rw 0 0 In kernel configuration DEBUG -g is disabled. -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: savecore problem
On Monday, March 16, 2015 11:54:52 AM Michael Jung wrote: On 2015-03-16 11:23, John Baldwin wrote: On Monday, March 16, 2015 10:17:54 AM Brandon Allbery wrote: On Mon, Mar 16, 2015 at 9:40 AM, Michael BlackHeart amdm...@gmail.com wrote: Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash (...) /dev/ufs/varfs /varufs rw,noatime 2 2 Last I checked, savecore had to happen very early --- before filesystems other than / are mounted. No, it can happen after that. What really has to happen is that you don't use swap (if you are dumping to your swap partition) before savecore runs. Can someone elaborate on not using swap as a dump device a little more? I have had instances in the past were I had issues with getting a core dump and resorted to a dedicated dump device but didn't investigate further nor have I read this as a requirement. Typically the first swap partition is used as the dump partition. If the system writes anything out to swap before savecore runs, then it can potentially overwrite part of the core. (Note that the running kernel doesn't know that there is a core on the swap partition to try to preserve, it just sees that there is an available swap partition.) To try to minimize the chances of this happening, the dump is written at the end of the swap partition instead of the start, but that is not foolproof. Usually you don't run too many things during early boot before savecore that would cause swapping, though a fsck of a large filesystem might use quite a bit of RAM which could result in swapping. A second question - Can a USB devices be used reliably for a dump device for ZFS on boot systems? I'm not sure if USB devices will work as a dump device or not. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
