3.4.0qa8 works fine, but after a while, a NetBSD/amd64 brick stops
responding (while NetBSD/i386 servers seems to work fine, therefore
it looks 64 bits specific). ktrace shows it loops around poll calls. Here
is what I can see if I stop it and inspect with gdb:
#0 0x7f7ff62759da in ___lwp
Yeah, a lot of threads are "missing"! Do the logs have anything unusual?
Avati
On Sun, Feb 3, 2013 at 7:00 AM, Emmanuel Dreyfus wrote:
> 3.4.0qa8 works fine, but after a while, a NetBSD/amd64 brick stops
> responding (while NetBSD/i386 servers seems to work fine, therefore
> it looks 64 bits sp
Anand Avati wrote:
> Yeah, a lot of threads are "missing"! Do the logs have anything unusual?
Nothing at all. It seems to be trashing its thread environment very
early: gdb will fail with a thread-related assertion when attaching it
even just after startup.
--
Emmanuel Dreyfus
http://hcpnet.f
On 01/31/2013 10:14 AM, Pranith Kumar K wrote:
hi Avati,
In entry self-heal of a directory, for every new file that is
created, data/metadata changelogs are marked on the source file to
indicate pending data/metadata self-heal from source file to the new
file that is created as part of t
