ffs snapshot lockup

Kris Kennaway kris at obsecurity.org
Wed Oct 4 19:42:04 UTC 2006


On Wed, Oct 04, 2006 at 01:06:37PM -0400, Vivek Khera wrote:
> 
> On Oct 4, 2006, at 12:39 PM, Kris Kennaway wrote:
> 
> >>>
> >>>The only thing I think was running at the time would be a large file
> >>>copy from a remote system to this one using rsync.
> >>
> >>As I understand, you got the panic. Then, you shall post the panic  
> >>message.
> >>If you have core file, then running kgdb on the core may show  
> >>required
> >>information.
> >>(it shall be on the console exactly before en
> >>and backtrace (using the bt command of ddb) of the paniced thread.
> >
> >YOu can also do 'show msgbuf' from DDB.
> >
> 
> i ran kgdb on the vmcore file.  since the dump was generated by  
> calling doadump from DDB, the backtrace was showing the call stack of  
> that.
> 
> 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.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20061004/df845d9f/attachment.pgp


More information about the freebsd-stable mailing list