Date: Fri, 22 Sep 2006 16:24:41 -0400 From: Vivek Khera <vivek@khera.org> To: stable@freebsd.org Subject: Re: ffs snapshot lockup Message-ID: <555B84D2-520F-44D6-84D6-CF9CE7EE47C7@khera.org> In-Reply-To: <20060922190328.GA64849@xor.obsecurity.org> References: <917B087C-5E13-4D7F-94FA-95CB0E5C1884@khera.org> <20060922190328.GA64849@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-11-260854879 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Sep 22, 2006, at 3:03 PM, Kris Kennaway wrote: >> I know this is very un-useful as a bug report, but I'm putting this >> out in case anyone else has noticed this. It has never happened to >> us before when we were running 5.4 and then 6.1 on this box. Nothing >> else changed on the system during this time. > > Yep, we'd need additional debugging to proceed. How does one debug a system where the disk sub-system is frozen? I have serial console with DDB/KDB built into the kernel and debugging symbols too. Is that the only option here? We're gonna try the full level 0 backup again monday and if it locks up I'll try to figure it out, but could use some hints as to where to poke in the kernel. --Apple-Mail-11-260854879--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?555B84D2-520F-44D6-84D6-CF9CE7EE47C7>