Daniel, Thanks for the explanation. Here is the config file. (See attached file: gpfs.ganesha.exports.conf)
with regards, Sachin Punadikar Ph. +91 - 20 - 42025693 Mob. +91 9890309049 email: psac...@in.ibm.com From: Daniel Gryniewicz <d...@redhat.com> To: nfs-ganesha-devel@lists.sourceforge.net Date: 03/29/2017 10:32 PM Subject: Re: [Nfs-ganesha-devel] What is PROTO_CLIENT client type ? It appears PROTO_CLIENT is a placeholder for an uninitialized entry in the client config list. Can you post the config for this failure. As for aborting, critical is not the same as fatal. In fact, major is worse than critical, and fatal is worse than major. In general, we don't abort on config errors for things that can be updated at runtime, such as exports or clients, since people with long-running instances don't want it to abort when config is updated, but would rather get an error that they can fix and retry, without cutting off existing connections. Daniel On 03/29/2017 08:10 AM, Sachin C Punadikar wrote: > Hi, > One of the Ganesha (Ganesha 2.2) user reported below kind of error: > > 2017-03-07T14:01:54.134482-06:00 mgmt002st001 nfs-ganesha[2197212]: > [work-236] LogClientListEntry :EXPORT :CRIT : 0x2320470 PROTO_CLIENT: > <unknown>(no_root_squash, RWrw, , , , > , , ) > 2017-03-07T14:01:54.145127-06:00 mgmt002st001 nfs-ganesha[2197212]: > [work-134] LogClientListEntry :EXPORT :CRIT : 0x2320470 PROTO_CLIENT: > <unknown>(no_root_squash, RWrw, , , , > , , ) > 2017-03-07T14:01:54.145956-06:00 mgmt002st001 nfs-ganesha[2197212]: > [work-163] LogClientListEntry :EXPORT :CRIT : 0x2320470 PROTO_CLIENT: > <unknown>(no_root_squash, RWrw, , , , > , , ) > > When I looked at the code, we do check all defined NFS clients (from the > export info) and report above critical error on finding any client > having type PROTO_CLIENT. This check is performed on every access to > that export. > I would like to know: > 1. What does it mean when the client type is PROTO_CLIENT ? > 2. Why the client definition can not have type PROTO_CLIENT ? > 3. If the error is critical, are we still supposed to continue to run > Ganesha or should exit ? > > with regards, > Sachin Punadikar > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
gpfs.ganesha.exports.conf
Description: Binary data
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
