LU-4805 lmv: lookup remote migrating object in LMV

If remote object is being found in a migrating directory,
it should continue to lookup the object in remote MDT,
instead of return.

Signed-off-by: wang di <di.wang@intel.com>
Change-Id: Ib3309e255e2e1fe5789854f47e470f3085d6f6e6
Reviewed-on: http://review.whamcloud.com/9806
Tested-by: Jenkins
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>

diff --git a/lustre/lmv/lmv_intent.c b/lustre/lmv/lmv_intent.c
index 57a6f94..1d8e927 100644 (file)
--- a/lustre/lmv/lmv_intent.c
+++ b/lustre/lmv/lmv_intent.c
@@ -492,7 +492,6 @@ int lmv_intent_lookup(struct obd_export *exp, struct md_op_data *op_data,
                it->d.lustre.it_disposition &= ~DISP_ENQ_COMPLETE;
                rc = md_intent_lock(tgt->ltd_exp, op_data, lmm, lmmsize, it,
                                    flags, reqp, cb_blocking, extra_lock_flags);
-               RETURN(rc);
        }
        /*
         * MDS has returned success. Probably name has been resolved in