[Glass] GS Fatal Internal Error, 5015, 15621, IO Error (RepRead Error)

Dale Henrichs dale.henrichs at gemtalksystems.com
Wed Jul 30 15:25:34 PDT 2014


You should be glad to know that based on your feedback and experience we
decided to turn on /dev/null tranlogs in some of our stress tests and have
indeed found some problems that could lead to the errors that you are
seeing ... no schedule for when the bugfixes will show up ...

BTW the fact that you never stopped/restarted your stone kinda sealed the
deal on implicating /dev/null tranlogs:)

So thanks for your patience and help in isolating the problem ...


On Tue, Jul 29, 2014 at 6:30 AM, <pieter at nagel.co.za> wrote:

> Dale,
> We're going to upgrade to or 3.2.1 first, and get back to you if
> the bug persists.
> But note that this bug only ever occured to stones that had never been
> shut down at all. In other words, to a pristine extent0 that was fired up,
> used to restore or had our code loaded to it, and had not yet the first
> shutdown of its lifetime.
> Once a stone was broken, not even stopstone could log in to it.
> Conversely, any stone that could be shutdown and restarted would
> thereafter be totally immune to this bug, in my experience.
> So I'm not sure if the shutdown code is involved here at all.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140730/717e8b15/attachment.html>

More information about the Glass mailing list