1297284 – Too many "failed to get the inode context for the inode" errors in brick logs

Bug 1297284 - Too many "failed to get the inode context for the inode" errors in brick logs

Summary: Too many "failed to get the inode context for the inode" errors in brick logs

Keywords:
Status:	CLOSED DUPLICATE of bug 1297300
Alias:	None
Product:	Red Hat Gluster Storage
Classification:	Red Hat Storage
Component:	bitrot
Sub Component:
Version:	rhgs-3.1
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Target Release:	---
Assignee:	Bug Updates Notification Mailing List
QA Contact:	RajeshReddy
Docs Contact:
URL:
Whiteboard:
Depends On:	1296399 1297300
Blocks:
TreeView+	depends on / blocked

Reported:	2016-01-11 05:57 UTC by Bhaskarakiran
Modified:	2016-09-17 14:23 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2016-01-11 07:34:24 UTC
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description Bhaskarakiran 2016-01-11 05:57:03 UTC

Description of problem:
=======================

A lot of bitrot error messages are seen in the brick logs.


[2016-01-09 08:10:31.194770] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode 1572c2f5-9917-423b-a987-86a7a78d342e
[2016-01-09 08:10:31.252071] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode 1572c2f5-9917-423b-a987-86a7a78d342e
[2016-01-09 08:10:31.288027] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode ba5f4b4c-2022-43c5-8d45-fa65ac8f3227
[2016-01-09 08:10:31.296192] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode b7b9d689-4b21-44eb-86c8-1c7f9f6b32ba
[2016-01-09 08:10:31.383698] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode ba5f4b4c-2022-43c5-8d45-fa65ac8f3227
[2016-01-09 08:10:31.501594] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode f7d80536-d2c1-48e0-a9de-0a7c3c55689b
[2016-01-09 08:10:31.566981] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode 9676610d-8d4b-4362-b230-6f2107050059
[2016-01-09 08:10:31.569765] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode f7d80536-d2c1-48e0-a9de-0a7c3c55689b
[2016-01-09 08:10:31.630599] E [MSGID: 116012] [bit-rot-stub.h:364:br_stub_is_bad_object] 0-disperse_vol1-bitrot-stub: failed to get the inode context for the inode 9676610d-8d4b-4362-b230-6f2107050059



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Bhaskarakiran 2016-01-11 06:12:58 UTC

Version:
========
3.7.5-15


https://bugzilla.redhat.com/show_bug.cgi?id=1296048 was filed and this bitrot issue seems to be a bigger issue. 


For the bitrot issues, upsteam bug is :https://bugzilla.redhat.com/show_bug.cgi?id=1297284

Note You need to log in before you can comment on or make changes to this bug.