Date: Wed, 4 Oct 2006 15:53:54 -0400 From: Vivek Khera <vivek@khera.org> To: stable@freebsd.org Subject: Re: ffs snapshot lockup Message-ID: <488B45BD-BBAA-4E5F-B94E-9DF27BFA1F3A@khera.org> In-Reply-To: <20061004194148.GA37672@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> <847DD3A5-D5DD-4D3E-B755-64B13D1DA506@khera.org> <20061003084315.GA89654@deviant.kiev.zoral.com.ua> <DFEA4E5F-2337-4383-8765-F5901BDA49E9@khera.org> <20061004140808.GD89654@deviant.kiev.zoral.com.ua> <20061004163944.GA35412@xor.obsecurity.org> <BB1FAD7A-1114-49D6-BC2E-C1B4B9D0C807@khera.org> <20061004194148.GA37672@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-16--851675655 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Oct 4, 2006, at 3:41 PM, Kris Kennaway wrote: >> from what i read in the output from kgdb, it seems that something >> locked the kernel and we broke to debugger from the watchdog timeout >> (I enable software watchdog). > > Hmm, be careful with that - if you set the timeout too low (and note > that for some workloads O(minutes) may even be too low) then you'll > get a lot of false positives. hmmm... the man page for watchdogd doesn't specify what the default timeout is, but that's what we've got running. [tappity-tapptity- tap...] source seems to indicate 16seconds timeout. interesting. so we could be getting hit with a bge interrupt storm and timing out. i'll turn off fido and see what happens. at this point, though, i think i have two separate issues. one with bge and watchdog timeout, and one with locking of the filesystem with mksnap_ffs, as the symptoms are different. --Apple-Mail-16--851675655--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?488B45BD-BBAA-4E5F-B94E-9DF27BFA1F3A>