Date: Sun, 13 Jun 2004 16:57:11 +0200 (CEST) From: Lukas Ertl <le@FreeBSD.org> To: Christian Hiris <4711@chello.at> Cc: freebsd-current@FreeBSD.org Subject: Re: HEADSUP: geom_vinum committed [Fatal trap 12 (g_event)] Message-ID: <20040613164837.O39575@leelou.in.tern> In-Reply-To: <200406131519.11988.4711@chello.at> References: <20040612232725.N35614@leelou.in.tern> <200406131519.11988.4711@chello.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Jun 2004, Christian Hiris wrote: > Unmounting the filesystem then panics the machine. I rebooted, did a 'fsck -t > ufs /dev/gvinum/vinum0', which results in a Fatal trap 12. So next I > recompiled kernel with the geom_subr.c.diff patch and debugging symbols. If it's possible for you please turn on INVARIANTS in your kernel, I've spread lots of KASSERTs around the code. > # Vinum configuration of matrix020.matrix.net, saved at Sat May 29 22:46:40 > 2004 > drive vinumdrive1 device /dev/da1s1h > drive vinumdrive0 device /dev/da0s1h > volume vinum0 > plex name vinum0.p0 org striped 558s vol vinum0 > sd name vinum0.p0.s0 drive vinumdrive0 plex vinum0.p0 len 35840340s > driveoffset 265s plexoffset 0s > sd name vinum0.p0.s1 drive vinumdrive1 plex vinum0.p0 len 35840340s > driveoffset 265s plexoffset 558s It would be also helpful if you could send me the on-disk config in private mail. Use something like: dd if=/dev/da1s1h skip=8 count=6 | tr -d '\000-\011\200-\377' to get it. > Stopped at redo_rank+0x70: cmpl $0,0xc(%edx) > db> trace > redo_rank(c2398e80,c1e63d80,d7e65cb0,c051b783,c1e63d80) at redo_rank+0x70 > g_detach(c1e63d80,c2398e80,4,0,d7e65cd8) at g_detach+0x67 > g_wither_geom(c2398e80,6,c20fc660,1,c06eb40d) at g_wither_geom+0xab > g_slice_spoiled(c1e63d80) at g_slice_spoiled+0x30 > g_spoil_event(c1e09400,0) at g_spoil_event+0x30 > one_event(d7e65d20,c051a58d,4b0,320,c1bf1898) at one_event+0x192 > g_run_events(4b0,320,c1bf1898,c051a56c,d7e65d34) at g_run_events+0x9 > g_event_procbody(0,d7e65d48) at g_event_procbody+0x21 Hm, I haven't seen this one before. It would be most helpful if you could get a crashdump and a backtrace from gdb -k to debug this. cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040613164837.O39575>