Bug 1396786

Summary: [Ganesha] : destroy_fsals CRIT messages in Ganesha logs
Product: Red Hat Gluster Storage Reporter: Ambarish <asoman>
Component: nfs-ganeshaAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED WONTFIX QA Contact: Manisha Saini <msaini>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.2CC: bturner, jthottan, kkeithle, rhinduja, rhs-bugs, skoduri, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: ---Flags: kkeithle: needinfo? (asoman)
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-19 06:50:51 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:

Description Ambarish 2016-11-20 06:36:40 UTC 
Description of problem:
-----------------------

4 node Ganesha cluster.Mounted a 2*2 volume on 4 clients via v3 .

Ran smallfile creates.

Seeing these messages in ganesha.log :

18/11/2016 10:47:59 : epoch d2110000 : gqas005.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-16239[Admin] destroy_fsals :FSAL :CRIT :Extra references (1) hanging around to FSAL PSEUDO

18/11/2016 10:47:59 : epoch d2110000 : gqas005.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-16239[Admin] destroy_fsals :FSAL :CRIT :Extra references (3) hanging around to FSAL GLUSTER

18/11/2016 10:47:59 : epoch d2110000 : gqas005.sbu.lab.eng.bos.redhat.com : ganesha.nfsd-16239[Admin] destroy_fsals :FSAL :CRIT :Extra references (3) hanging around to FSAL GLUSTER

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

glusterfs-ganesha-3.8.4-5.el7rhgs.x86_64
nfs-ganesha-2.4.1-1.el7rhgs.x86_64


How reproducible:
----------------

Every which way I try.

Steps to Reproduce:
-------------------

1. Create a new 2*2 volume ,mount it via v3 on 4 clients.

2. Run smallfile creates in  a distributed multithreaded way.

3. Check Ganesha logs.

Actual results:
---------------


Expected results:
-----------------

Need confirmation from Dev if this is expected.

Additional info:
----------------


Volume Name: testvol
Type: Distributed-Replicate
Volume ID: 865c5329-7fa5-4a10-888b-671902b0bca6
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: gqas013.sbu.lab.eng.bos.redhat.com:/bricks/testvol_brick0
Brick2: gqas005.sbu.lab.eng.bos.redhat.com:/bricks/testvol_brick1
Brick3: gqas006.sbu.lab.eng.bos.redhat.com:/bricks/testvol_brick2
Brick4: gqas011.sbu.lab.eng.bos.redhat.com:/bricks/testvol_brick3
Options Reconfigured:
ganesha.enable: on
features.cache-invalidation: on
nfs.disable: on
performance.readdir-ahead: on
transport.address-family: inet
performance.stat-prefetch: off
server.allow-insecure: on
diagnostics.latency-measurement: on
diagnostics.count-fop-hits: on
nfs-ganesha: enable
cluster.enable-shared-storage: enable
[root@gqas013 ~]#
Comment 3 Jiffin 2016-11-20 07:11:21 UTC 
destroy_fsal should be called during ganesha stop or unexporting the volume. Do u perform any operations like that?
Comment 4 Ambarish 2016-11-20 07:55:53 UTC 
I never restarted ganesha service during my tests.
Nor did I restart the volume.
Comment 5 Ambarish 2016-11-20 07:59:17 UTC 
Jiffin,

Sorry.I take that back.
I did restart ganesha services,after making changes to ganesha-<volname>.conf
Comment 9 Kaleb KEITHLEY 2017-08-23 12:35:21 UTC 
please see if you can reproduce in rhgs-3.3.0