ffs snapshot lockup
Peter Holm
peter at holm.cc
Thu Oct 5 04:51:47 UTC 2006
On Wed, Oct 04, 2006 at 03:41:48PM -0400, Kris Kennaway wrote:
> 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.
>
Oh, yes. I've using this with success:
watchdogd -t 3600 -e 'ls /tmp /dev > /dev/null; true' -s 60
- Peter
> Kris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (FreeBSD)
>
> iD8DBQFFJA58Wry0BWjoQKURAr5dAKDf4YLcBJU9owRw6N1L3FcgJkvOOgCfRQkq
> bd8+tGZVB28bkYBN6KL7iO0=
> =B7Vl
> -----END PGP SIGNATURE-----
More information about the freebsd-stable
mailing list