LU-9995 lfsck: Have LMV_HASH_FLAG_DEAD defined for a while longer

LMV_HASH_FLAG_DEAD is still used in lfsck and not to make any hasty
moves, just move the version check arount that define further away
while we are examining what really needs to be done there.

This unbreaks the build breakage from 2.10.53 tag.

Change-Id: I87b25136f8fc03e59aed97352567757d2460ab3a
Signed-off-by: Oleg Drokin <oleg.drokin@intel.com>

diff --git a/lustre/include/uapi/linux/lustre/lustre_idl.h b/lustre/include/uapi/linux/lustre/lustre_idl.h
index f124baa..530e058 100644 (file)
--- a/lustre/include/uapi/linux/lustre/lustre_idl.h
+++ b/lustre/include/uapi/linux/lustre/lustre_idl.h
@@ -2084,7 +2084,7 @@ struct lmv_mds_md_v1 {
 
 #define LMV_HASH_FLAG_MIGRATION        0x80000000
 
 
 #define LMV_HASH_FLAG_MIGRATION        0x80000000
 

-#if LUSTRE_VERSION_CODE < OBD_OCD_VERSION(2, 10, 53, 0)
+#if LUSTRE_VERSION_CODE < OBD_OCD_VERSION(2, 10, 56, 0)

 /* Since lustre 2.8, this flag will not be needed, instead this DEAD
  * and orphan flags will be stored in LMA (see LMAI_ORPHAN)
  * Keep this flag just for LFSCK, because it still might meet such
 /* Since lustre 2.8, this flag will not be needed, instead this DEAD
  * and orphan flags will be stored in LMA (see LMAI_ORPHAN)
  * Keep this flag just for LFSCK, because it still might meet such