inode context is NULL in io-cache

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I might have to test the ctdb setup again and see if io-cache enabling with
the fix he mentioned fixes the ctdb failover with io-cache.


On Mon, Aug 26, 2013 at 6:10 PM, Joe Julian <joe at julianfamily.org> wrote:

> On 08/26/2013 02:32 PM, Joe Julian wrote:
>
>> Are these really errors? I have a massive number of them in my logs.
>>
>> E [io-cache.c:557:ioc_open_cbk] 0-mysql1-io-cache: inode context is NULL
>> (b24d4411-ead1-49f7-bf40-**62e9c969eb2d)
>>
>> If they are errors, what's broken?
>> ______________________________**_________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://supercolony.gluster.**org/mailman/listinfo/gluster-**users<http://supercolony.gluster.org/mailman/listinfo/gluster-users>
>>
> Avati answered this in #gluster:
>
>  it's a "safe" error.. it is fixed in master branch and requires a
>> backport to 3.4
>> related to readdirplus code changes
>> you specifically need commit 2991503d014f634da5cd10bcb851e9**86a3dcd5c2
>>
>
> ______________________________**_________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.**org/mailman/listinfo/gluster-**users<http://supercolony.gluster.org/mailman/listinfo/gluster-users>
>



-- 
*Religious confuse piety with mere ritual, the virtuous confuse regulation
with outcomes*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130826/27291347/attachment.html>


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux