Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: "mdc_lookup" do not dispatch to FSAL

Bill, The issue is always re-producible for the customer. In another email chain, I have provided the Ganesha logs, which clearly indicates the lookup do not goes to FSAL layer to fetch the more current data if uncached is set to false. On Fri, Feb 16, 2018 at 9:40 PM, William Allen Simpson <

Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: "mdc_lookup" do not dispatch to FSAL

On 2/19/18 12:12 PM, Sachin Punadikar wrote: Hi Bill, I rechecked the logs & discussed with Daniel. I missed to see the log entries related to FSAL. So for this customer it looks like FSAL issue than a Ganesha issue Thanks for the update. The default log levels don't always show enough.

Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: "mdc_lookup" do not dispatch to FSAL

On 2/15/18 6:44 AM, GerritHub wrote: Sachin Punadikar has uploaded this change for *review*. View Change "mdc_lookup" do not dispatch to FSAL Are you sure? Do you have an actual reproducible error case? "mdc_lookup" function first attempts to get the

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: "mdc_lookup" do not dispatch to FSAL

>From Sachin Punadikar : Sachin Punadikar has uploaded this change for review. ( https://review.gerrithub.io/400037 Change subject: "mdc_lookup" do not dispatch to FSAL .. "mdc_lookup" do not dispatch to