[Gluster-devel] post 3.1 xlator/io-threads instability on NetBSD (was: NULL frame->conn cause a crash)

Vijay Bellur vijay at gluster.com
Wed Jul 6 17:40:45 UTC 2011

On Wed, Jul 6, 2011 at 8:41 PM, Emmanuel Dreyfus <manu at netbsd.org> wrote:

> On Tue, Jul 05, 2011 at 09:32:23AM +0000, Emmanuel Dreyfus wrote:
> > Let us forget my previous batch of crashes that were with 3.2.1. This
> > one iw with today's code from git:
> I made some progress on that problem. Removing the io-threads xlator
> fixes the stability problem.

I guess you might have seen the stability problem due to threads racing. Can
you run glusterfsd processes with valgrind and observe the reports/core
generated thus? The crash that you posted yesterday does seem to indicate a
memory corruption.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20110706/d4c737cb/attachment-0003.html>

More information about the Gluster-devel mailing list