From owner-freebsd-stable@FreeBSD.ORG Tue Mar 17 14:58:29 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFFF2B01 for ; Tue, 17 Mar 2015 14:58:29 +0000 (UTC) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE4D095C for ; Tue, 17 Mar 2015 14:58:29 +0000 (UTC) Received: by oigv203 with SMTP id v203so10354941oig.3 for ; Tue, 17 Mar 2015 07:58:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ENBR6skdrQpM8HwsBq6UYWW933X9f6BGlOw/BxEGV1c=; b=dbq+kfBdJc0AKTxbLWA4BXnX8TnCY2OtwhFj6fRTy+fnrNg4ABLHpQBPVDtFRgfEjP 6nb+i64oiKrSN39KTcOmO9SIGf4ZjtJWqn2GGXgawWFyXKf+RM5/5P917cCc4H5zgfY2 HngZGBPYbvqNbwR7+VVff96Or91Y+Vl4kzU21iLnhwc96TLiQMZ/a6kUCI2RxOMDFUWT vnDOJ1DMoXX6X9srkU0BRZP5U31luCdw3K4alR5JGI3BxPxTb2sbF7VmI3MP7w1SfJnc yjat2FKF8zks5yDkrdELsNBtEC6IAdph0OblEB25hSE63/+NCdyRs7TdjZsNf+4rFDnx IlSQ== MIME-Version: 1.0 X-Received: by 10.182.121.225 with SMTP id ln1mr53112367obb.65.1426604308768; Tue, 17 Mar 2015 07:58:28 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.215.7 with HTTP; Tue, 17 Mar 2015 07:58:28 -0700 (PDT) In-Reply-To: References: Date: Tue, 17 Mar 2015 08:58:28 -0600 X-Google-Sender-Auth: H_lD5rWrOmdULEN8JfMMQQOJseo Message-ID: Subject: Re: savecore problem From: Alan Somers To: Michael BlackHeart Content-Type: text/plain; charset=UTF-8 Cc: Konstantin Kulikov , freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 14:58:30 -0000 On Mon, Mar 16, 2015 at 12:06 PM, Michael BlackHeart 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 : > >> 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 >> 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 >> > >> > # Device Mountpoint FStype Options >> > Dump Pass# >> > /dev/ufs/rootfs / ufs rw,noatime >> > 1 1 >> > /dev/raid/r0p3 none swap sw >> > 0 0 >> > /dev/ufs/varfs /var ufs rw,noatime >> > 2 2 >> > /dev/ufs/tmpfs /tmp ufs rw,noatime >> > 2 2 >> > /dev/ufs/usrfs /usr ufs 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-unsubscribe@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-unsubscribe@freebsd.org"