[Bugs] [Bug 1445260] New: [GANESHA] Volume start and stop having ganesha enable on it, turns off cache-invalidation on volume

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1445260

            Bug ID: 1445260
           Summary: [GANESHA] Volume start and stop having ganesha enable
                    on it,turns off cache-invalidation on volume
           Product: GlusterFS
           Version: 3.10
         Component: glusterd
          Priority: high
          Assignee: jthottan at redhat.com
          Reporter: jthottan at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org,
                    msaini at redhat.com, rhinduja at redhat.com,
                    rhs-bugs at redhat.com, skoduri at redhat.com,
                    storage-qa-internal at redhat.com, vbellur at redhat.com
        Depends On: 1443990
            Blocks: 1417151



+++ This bug was initially created as a clone of Bug #1443990 +++

Description of problem:
Volume having ganesha enable on it,after performing volume stop and start turns
of features.cache-invalidation to off

Version-Release number of selected component (if applicable):
# rpm -qa | grep ganesha
glusterfs-ganesha-3.8.4-22.el7rhgs.x86_64
nfs-ganesha-2.4.4-2.el7.x86_64
nfs-ganesha-gluster-2.4.4-2.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Create 4 node ganesha cluster.
2.Create a volume.Enable ganesha on it
3.Do volume stop and start


Actual results:
features.cache-invalidation gets turned off while doing volume stop and start.
Volume is still exported after restart

Expected results:
features.cache-invalidation should not be turned off after doing volume start
and stop

Additional info:

While ganesha is enabled on fresh volume
====

# gluster v info

Volume Name: ganesha1
Type: Distributed-Replicate
Volume ID: 793f86f4-7e0b-4b0d-a4e5-4fb8ab9b82c0
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: dhcp47-132.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick2: dhcp47-141.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick3: dhcp47-144.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick4: dhcp47-139.lab.eng.blr.redhat.com:/gluster/brick1/1
Options Reconfigured:
ganesha.enable: on
features.cache-invalidation: on
transport.address-family: inet
nfs.disable: on
cluster.brick-multiplex: disable
nfs-ganesha: enable
cluster.enable-shared-storage: enable


======

After performing volume stop and start

# gluster v info

Volume Name: ganesha1
Type: Distributed-Replicate
Volume ID: 793f86f4-7e0b-4b0d-a4e5-4fb8ab9b82c0
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: dhcp47-132.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick2: dhcp47-141.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick3: dhcp47-144.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick4: dhcp47-139.lab.eng.blr.redhat.com:/gluster/brick1/1
Options Reconfigured:
ganesha.enable: on
features.cache-invalidation: off
transport.address-family: inet
nfs.disable: on
cluster.brick-multiplex: disable
nfs-ganesha: enable
cluster.enable-shared-storage: enable


# showmount -e localhost
Export list for localhost:
/ganesha1 (everyone)



--- Additional comment from Jiffin on 2017-04-21 06:41:25 EDT ---

Looks like a genuine bug to me(not regression, day one issue)

When volume stop is performed we call ganesha_manage_export() with value =off .
This will internally turn off cache-invalidation. During start we export volume
via hook script but never turn on this option.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1443990
[Bug 1443990] [GANESHA] Volume start and stop having ganesha enable on
it,turns off cache-invalidation on volume
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=z8ZczeTW8V&a=cc_unsubscribe