LU-9340 lov: Initialize component extents unconditionally

LOV should initialize extent of components even they are not
instantiated because lov_io_iter_init() relies on this to issue
write intent RPC.

Signed-off-by: Jinshan Xiong <jinshan.xiong@intel.com>
Change-Id: Iaa452e3a0f3186cfea77866b7a1fabbc9feeec53
Reviewed-on: https://review.whamcloud.com/27097
Tested-by: Jenkins
Reviewed-by: Bobi Jam <bobijam@hotmail.com>
Reviewed-by: Niu Yawei <yawei.niu@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>

diff --git a/lustre/lov/lov_object.c b/lustre/lov/lov_object.c
index 3a9eb87..65e20be 100644 (file)
--- a/lustre/lov/lov_object.c
+++ b/lustre/lov/lov_object.c
@@ -310,7 +310,7 @@ static int lov_init_composite(const struct lu_env *env, struct lov_device *dev,
                 * will be dynamically init-ed later on file write/trunc ops.
                 */
                if (!lsm_entry_inited(lsm, i))
-                       break;
+                       continue;
 
                result = lov_init_raid0(env, dev, lov, i, &le->lle_raid0);
                if (result < 0)