Bug 1021665

Summary:	[quota] - Error "0-quota-test-setup-client-1: this function should not be called" seen in quotad.log.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Ben Turner <bturner>
Component:	quota	Assignee:	Raghavendra G <rgowdapp>
Status:	CLOSED DEFERRED	QA Contact:	Ben Turner <bturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	nsathyan, rhinduja, rhs-bugs, storage-qa-internal, vagarwal, vbellur, vmallika
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1282717 (view as bug list)		Environment:
Last Closed:	2015-11-17 08:46:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1282717

Description Ben Turner 2013-10-21 18:30:45 UTC

Description of problem:

After enabling quota and setting a hard limit in the logs I see:

[2013-10-21 16:59:32.044155] W [client-callback.c:31:client_cbk_fetchspec] 0-quota-test-setup-client-1: this function should not be called

I am not seeing any ill effects but the error message makes me think that this function shouldn't be getting called.

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

glusterfs-3.4.0.35rhs-1.el6rhs.x86_64

How reproducible:

Every time.

Steps to Reproduce:
1.  Enable quota
2.  Set a quota
3.  check quotad.log

Actual results:

[2013-10-21 16:59:32.044155] W [client-callback.c:31:client_cbk_fetchspec] 0-quota-test-setup-client-1: this function should not be called
[2013-10-21 16:59:32.044176] W [client-callback.c:31:client_cbk_fetchspec] 0-quota-test-setup-client-3: this function should not be called
[2013-10-21 16:59:32.044221] W [client-callback.c:31:client_cbk_fetchspec] 0-quota-test-setup-client-5: this function should not be called

Expected results:

Either:

1. Change the warning to something more meaningful/representative of the waring you wish to portray.

2.  If we really should not be calling that function, don't call it.

Additional info:

Comment 2 Rahul Hinduja 2014-05-22 12:52:58 UTC

Same errors were reported in nfs.log and glustershd.log as well

[root@snapshot13 ~]# cat /var/log/glusterfs/glustershd.log | grep "this function should not be called"
[2014-05-22 10:11:13.870162] W [client-callback.c:31:client_cbk_fetchspec] 0-vol1-client-2: this function should not be called
[2014-05-22 10:12:55.189753] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:12:55.272518] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:12:55.338072] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:12:55.402254] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:12:55.468105] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:12:57.645644] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:12:58.835096] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:12:59.895354] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:12:59.958646] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called
[2014-05-22 10:13:00.024091] W [client-callback.c:31:client_cbk_fetchspec] 0-vol2-client-3: this function should not be called




[root@snapshot13 ~]#  cat /var/log/glusterfs/nfs.log | grep "this function should not be called"
[2014-05-22 10:12:55.189753] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:12:55.272489] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:12:55.338118] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:12:55.402277] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:12:55.468125] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:12:57.645652] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:12:58.835140] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:12:59.895464] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:12:59.958750] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called
[2014-05-22 10:13:00.024091] W [client-callback.c:31:client_cbk_fetchspec] 0-vol3-client-3: this function should not be called


Steps after which the error is reported:


1. Create and start 4 volumes (2*2) from 4 nodes
2. Mount the volumes (Fuse and NFS)
3. Create data from fuse and nfs client
4. Create a snapshot of volume
5. kill glusterd on node2
6. bring down the node4(poweroff)
7. offline the volume from node1 (gluster volume stop volume)
8. Restore the volume to snapshot taken at step2
9. Start the glusterd on node2
10. bring back the node4

Observed both nfs.log and glustershd.log reported these errors

Comment 4 Vijaikumar Mallikarjuna 2015-11-17 08:46:27 UTC

As 2.1 is EOL'ed, closing this bug and filed 3.1 bug# 1282717