LU-9437 lfsck: handle LMV EA for migrating directory
For the in-migration directory, its LMV EA contains not only the
LMV header, but also the FIDs for both source and target. So the
LMV EA size is larger. The lfsck_read_stripe_lmv() logic need to
handle such case properly.
Lustre-change: https://review.whamcloud.com/31266
Lustre-commit:
05cfe91c2714a77f5ad3de4a7e58e20b6df17b83
Signed-off-by: Fan Yong <fan.yong@intel.com>
Change-Id: Ic43853fb5ca058042fafa0f6c81fa99d4b8d8897
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Lai Siyao <lai.siyao@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/31518
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>