+++ This bug was initially created as a clone of Bug #1419870 +++ Description of problem: inode_dump is not generated in statedump after send USR1 signal or through cli for gluster/nfs process. Version-Release number of selected component (if applicable): ALL How reproducible: Always Steps to Reproduce: 1.Setup gluster/nfs environment after off nfs.disable 2.send USR1 signal or run gluster v statedump <v-name> nfs to generate statedump 3.statedump does not show inode data Actual results: statedump does not show any inode data. Expected results: It should show inode data. Additional info: --- Additional comment from Worker Ant on 2017-02-07 23:26:55 EST --- REVIEW: https://review.gluster.org/16559 (Problem: inode_dump is not generated in statedump for gluster/nfs process) posted (#1) for review on master by MOHIT AGRAWAL (moagrawa) --- Additional comment from Worker Ant on 2017-02-08 01:47:26 EST --- REVIEW: https://review.gluster.org/16559 (core: inode_dump is not generated in statedump for gluster/nfs process) posted (#2) for review on master by MOHIT AGRAWAL (moagrawa) --- Additional comment from Worker Ant on 2017-02-08 08:21:06 EST --- REVIEW: https://review.gluster.org/16559 (Problem: inode_dump is not generated in statedump for gluster/nfs process) posted (#3) for review on master by MOHIT AGRAWAL (moagrawa) --- Additional comment from Worker Ant on 2017-02-08 23:02:44 EST --- REVIEW: https://review.gluster.org/16559 (Problem: inode_dump is not generated in statedump for gluster/nfs process) posted (#4) for review on master by MOHIT AGRAWAL (moagrawa)
upstream patch : https://review.gluster.org/16559
Thank you for your report. This bug is filed against a component for which no further new development is being undertaken