Hiroki Sato <h...@freebsd.org> wrote in <20110911.054601.1424617155148336027....@allbsd.org>:
hr> Hiroki Sato <h...@freebsd.org> wrote hr> in <20110910.044841.232160047547388224....@allbsd.org>: hr> hr> hr> Hiroki Sato <h...@freebsd.org> wrote hr> hr> in <20110907.094717.2272609566853905102....@allbsd.org>: hr> hr> hr> hr> hr> During this investigation an disk has to be replaced and resilvering hr> hr> hr> it is now in progress. A deadlock and a forced reboot after that hr> hr> hr> make recovering of the zfs datasets take a long time (for committing hr> hr> hr> logs, I think), so I will try to reproduce the deadlock and get a hr> hr> hr> core dump after it finished. hr> hr> hr> hr> I think I could reproduce the symptoms. I have no idea about if hr> hr> these are exactly the same as occurred on my box before because the hr> hr> kernel was replaced with one with some debugging options, but these hr> hr> are reproducible at least. hr> hr> hr> hr> There are two symptoms. One is a panic. A DDB output when the panic hr> hr> occurred is the following: hr> hr> I am trying vfs.lookup_shared=0 and seeing how it goes. It seems the hr> box can endure a high load which quickly caused these symptoms. There was no difference by the knob. The same panic or unresponsiveness still occurs in about 24-32 hours or so. -- Hiroki
pgpIwsQ57ZO6Q.pgp
Description: PGP signature
