Date: Mon, 25 May 2009 21:37:34 +1000 From: David N <davidn04@gmail.com> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: gjournal locks up Message-ID: <4d7dd86f0905250437u63b9152m65a914b7acd3f0@mail.gmail.com> In-Reply-To: <gvduv1$qkp$1@ger.gmane.org> References: <4d7dd86f0905250042v61f2af6cl943b665cdbeb26a3@mail.gmail.com> <gvdkaa$qs4$1@ger.gmane.org> <4d7dd86f0905250339o6e395102l5074198b38143970@mail.gmail.com> <gvdtes$lu3$1@ger.gmane.org> <4d7dd86f0905250415u32171606qaf9b64185da1a50@mail.gmail.com> <gvduv1$qkp$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/5/25 Ivan Voras <ivoras@freebsd.org>: > David N wrote: >> 2009/5/25 Ivan Voras <ivoras@freebsd.org>: >>> David N wrote: >>> >>>> The first time it locked up was when i was copying >>>> cp -va >>>> from one disk (degraded mirrror) to the other disk (degraded mirror + >>>> gjournal). Copied around 40GB until it locked up. It did it 3 times >>>> before i manage to copy everything over. Re-syncing of the mirror >>>> works fine. >>>> >>>> Should i use >>>> options KDB >>>> options DDB >>>> options INVARIANTS >>>> options INVARIANTS_SUPPORT >>>> options WITNESS >>>> options DIAGNOSTIC >>>> ? >>> You can leave DIAGNOSTIC out. >>> >>> I'd still like you to post process' states (wchan) - in your case, of >>> the "cp" process. >> >> How would i go about doing that? >> Sorry, I'm new to debugging FreeBSD, been using for a long time though. > > You can see them in "top" or you can do "ps axul". > > Before the lock up all disk activity come to a halt. Gstat - all disk drops to 0.00 then locks More info can be seen http://lists.freebsd.org/pipermail/freebsd-questions/2009-May/198149.html I'll post more info when the new kernel is done. Regards David N
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d7dd86f0905250437u63b9152m65a914b7acd3f0>