Date: Tue, 26 May 2009 16:24:41 +0200 From: "Johan Hendriks" <Johan@double-l.nl> To: "Florian Smeets" <flo@kasimir.com> Cc: freebsd-current@FreeBSD.org Subject: RE: ZFS Crash Message-ID: <57200BF94E69E54880C9BB1AF714BBCB5DE8B0@w2003s01.double-l.local> References: <alpine.BSF.2.00.0905250040230.1781@borg> <3c1674c90905242253n544c3f0cqb10952f349391ce7@mail.gmail.com> <454b8cc37c60ab7af2663ba70ddbfd59.squirrel@webmail.lerctr.org> <5a9a181a12e9e4ef864d23ae063f7277.squirrel@webmail.lerctr.org> <alpine.BSF.2.00.0905250803350.79867@borg><alpine.BSF.2.00.0905260702300.1820@borg> <4A1BE241.5030706@kasimir.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>On 26.05.09 14:04, Larry Rosenman wrote: >> On Mon, 25 May 2009, Larry Rosenman wrote: >> >>> On Mon, 25 May 2009, Larry Rosenman wrote: >>> >>>> after looking at the code, never mind the "don't call doadump", so = we'll >>>> get the textdump. >>>> >>>> Thanks rwatson for the textdump stuff! >>>> >>> Here is current stats before we crash. Does any of this look totally >>> out of line? >>> >> It crashed again, but did *NOT* make it into ddb enough to do the = textdump. >> >> It was hung with the backtrace (looks like the same, but I couldn't >> scroll the screen back). >> >> Ideas? >> >> I'm really concerned that there is a problem. >> >Hi i guess I'm having a similar/the same problem. The panic looks the=20 >same, and the trace is a little different, I've had a lot of these=20 >panics on this machine, and the stack trace looked different quite = often. >The panic and show uma and show malloc can be found here:=20 >http://webmail.solomo.de/~flo/panic.txt >I have a coredump written to swap, but this panic is very easy to=20 >trigger and it panics every time savecore runs... It is also easy to=20 >trigger this with a buildworld -j5. >This is a quadcore Xeon with a a slow SATA disk and only 1GB of mem.=20 >(It's only a test machine, so i can test any suggestion.) This box used = >to run stable with kmem max set to 768M. >Anything i can do? >Cheers, >Florian I have several panics also i am using cvsup-mirror on a zfs raidz2. It did run good for quite some time, but last week after a buildworld it = started to panic as soon as /usr/local/etc/cvsup/update.sh was running. I had vm.kmem_size=3D"512M" and vm.kmem_size_max=3D"512M". I had a custom kernel with some options added and some taken off. The box is a HP Proliant 110 with 1GB memory and is running the amd64 = version of FreeBSD. =20 My custom kernel had the following. # Debugging for use in -current nooptions KDB # Enable kernel debugger support. nooptions DDB # Support DDB. nooptions GDB # Support remote GDB. nooptions INVARIANTS # Enable calls of extra sanity checking nooptions INVARIANT_SUPPORT # Extra sanity checks of internal = structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect deadlocks and = cycles nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks for = speed #polling options DEVICE_POLLING # pf options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_CDNR options ALTQ_PRIQ device pf device pflog device pfsync I did a new buildworld with a GENERIC kernel with pf part still there. = But now i can not panic it again. So maybe it is the options DEVICE_POLLING option. i will try to add that again to the kernel and try to panic it again. Do you have the DEVICE_POLLING option in your kernel? BTW i am no FreeBSD or debug expert. This is just an observation. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com=20 Version: 8.5.339 / Virus Database: 270.12.39/2134 - Release Date: = 05/25/09 18:14:00
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57200BF94E69E54880C9BB1AF714BBCB5DE8B0>