+++ This bug was initially created as a clone of Bug #1174170 +++
+++                                                           +++
+++ Use this bug to include a fix in the master branch.       +++

Description of problem:
We are getting quite a lot of warnings and error messages in our brick logs. The installed glusterfs version is 3.6.1 on a CentOS 6 machine.

Disabling the quota system fixes the output problem. We didn't really see any actual negative impact from these messages, but didn't try to hard yet either. Quota limit worked tho.

After disabling and reenabling quota, we also get the following messages:
E [marker.c:2542:marker_removexattr_cbk] 0-data-marker: No data available occurred while creating symlinks

Brick log output:
2014-12-15 09:06:10.175551] W [marker.c:2752:marker_readdirp_cbk] 0-data-marker: Couln't build loc for 9d0bc464-2fe3-4320-b4a1-ce46d829d073/99998.jpeg
[2014-12-15 09:06:10.175773] E [inode.c:1151:__inode_path] (--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x1e0)[0x7f35536de420] (--> /usr/lib64/libglusterfs.so.0(__inode_path+0x2ae)[0x7f35536fd17e] (--> /usr/lib64/libglusterfs.so.0(inode_path+0x4a)[0x7f35536fd25a] (--> /usr/lib64/glusterfs/3.6.1/xlator/features/marker.so(marker_inode_loc_fill+0x7a)[0x7f35420d6e0a] (--> /usr/lib64/glusterfs/3.6.1/xlator/features/marker.so(marker_readdirp_cbk+0x1e1)[0x7f35420d7031] ))))) 0-: Assertion failed: 0
[2014-12-15 09:06:10.175998] W [inode.c:1152:__inode_path] (--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x1e0)[0x7f35536de420] (--> /usr/lib64/libglusterfs.so.0(__inode_path+0x2e2)[0x7f35536fd1b2] (--> /usr/lib64/libglusterfs.so.0(inode_path+0x4a)[0x7f35536fd25a] (--> /usr/lib64/glusterfs/3.6.1/xlator/features/marker.so(marker_inode_loc_fill+0x7a)[0x7f35420d6e0a] (--> /usr/lib64/glusterfs/3.6.1/xlator/features/marker.so(marker_readdirp_cbk+0x1e1)[0x7f35420d7031] ))))) 0-data-marker: invalid inode
[2014-12-15 09:06:10.176028] W [marker.c:2752:marker_readdirp_cbk] 0-data-marker: Couln't build loc for 9d0bc464-2fe3-4320-b4a1-ce46d829d073/99999.jpeg

# gluster volume info
Volume Name: data
Type: Replicate
Volume ID: 34411f11-0cb7-43a4-adca-80a237694406
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: gluster1:/data/brick0/brick
Brick2: gluster2:/data/brick0/brick
Options Reconfigured:
diagnostics.brick-log-level: WARNING
performance.cache-size: 2048MB
performance.write-behind-window-size: 512MB
performance.flush-behind: on
features.quota: on
performance.stat-prefetch: on

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

How reproducible:
Every time on our configuration, but we didn't set up a test cluster to try it out.

Steps to Reproduce:
1. We simply enable quota and the messages appear.

Actual results:
The log output above.

Expected results:
No warnings/errors in brick log.

--- Additional comment from Jan-Hendrik Zab on 2014-12-15 11:18:27 CET ---

The patch was supplied by Niels de Vos, it should stop the logging, but it doesn't fix the actual problem.

So far, we couldn't test the patch on our production system.

--- Additional comment from Niels de Vos on 2014-12-15 11:31:03 CET ---

This issue has been made visible with http://review.gluster.org/8296 , adding Varun and Raghavendra on CC so that they can check if a readdirp_cbk() with an entry->inode == NULL is valid in the 1st place.