Soumya Koduri [[email protected]] wrote: > The issue was with 'clustered' config option. If this option is set, > nfs-ganesha writes the clients state to '/var/lib/nfs/ganesha/node{id}' > directory. Since we need IP based solution, we had to turn off this > config option though we have a cluster of nfs-ganesha nodes. > > If I remember from the discussion we had, you had agreed to de-couple > this option from node-id so that this option can in general be used by > anyone planning to have a cluster (and not using node-IDs). And sorry I > have't got time to check on that later, but shall be able to look it (in > a couple of weeks time) if you would like me to work on it.
If I remember right, "clustered" really has nothing special about it other than storing state in "recovery-dir/node<id>". You wanted to store it in "recovery-dir/IP" which is the default if "clustered" is false. Do you expect anything other than node or IP based directory scheme. If so, we could just have "recovery_type(enum, values [ip,nodeid], default ip)" in the config. We can phase out clustered keyword altother to not confuse people. If someone wants nodeid/IP, then we can add nodeidip as well to the above enum. Regards, Malahal. ------------------------------------------------------------------------------ _______________________________________________ Nfs-ganesha-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
