Date: Mon, 16 Mar 2015 21:06:20 +0300 From: Michael BlackHeart <amdmiek@gmail.com> To: Konstantin Kulikov <k.kulikov2@gmail.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: savecore problem Message-ID: <CA%2BAz77NOaZW5hkNmMLmnE3kO4OpxxHErqxP2kKZyxgLvdRFyRw@mail.gmail.com> In-Reply-To: <CAD%2BeXGRtrfx=Mw_KNTn2THxKqguKyHVn45%2BV8k3aWnQDpy2HSg@mail.gmail.com> References: <CA%2BAz77No%2B0k=S4xq5MPK-YEgm7HGh%2B%2BSBNRHeV0hHq7AqOc0Tw@mail.gmail.com> <CAD%2BeXGRtrfx=Mw_KNTn2THxKqguKyHVn45%2BV8k3aWnQDpy2HSg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.kulikov2@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 <amdmiek@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 > > > > # 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BAz77NOaZW5hkNmMLmnE3kO4OpxxHErqxP2kKZyxgLvdRFyRw>