Date: Mon, 25 Sep 2006 14:30:28 -0400 From: Vivek Khera <vivek@khera.org> To: stable@freebsd.org Subject: Re: ffs snapshot lockup Message-ID: <A53470AA-50AF-4CB4-96BC-12B11729BB6C@khera.org> In-Reply-To: <20060922203654.GA65693@xor.obsecurity.org> References: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> <20060922190328.GA64849@xor.obsecurity.org> <555B84D2-520F-44D6-84D6-CF9CE7EE47C7@khera.org> <20060922203654.GA65693@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-11-513202248 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Sep 22, 2006, at 4:36 PM, Kris Kennaway wrote: > Start by enabling INVARIANTS, INVARIANT_SUPPORT, DEBUG_LOCKS and > DEBUG_VFS_LOCKS, then run 'show lockedvnods' and 'alltrace' in DDB > (spammy, need that serial console), or at least trace the running > processes (show allpcpu) and those listed in lockedvnods. Then call > doadump and save the core+kernel.debug when you reboot. Well, it happened again (as I was building the debugging kernel, no less)... but it only locked up one file system not the whole box. So my home dir was wedged, and everything trying to use anyone's home dir was wedged, but /usr and / were still responding. So now I do have the kernel in place and the serial console is already there and your notes on what to do are there, so next time it happens I'm ready! --Apple-Mail-11-513202248--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A53470AA-50AF-4CB4-96BC-12B11729BB6C>