Whamcloud - gitweb
LU-8929 lfsck: dumper gets current position properly 69/24869/2
authorFan Yong <fan.yong@intel.com>
Tue, 27 Sep 2016 15:12:12 +0000 (23:12 +0800)
committerOleg Drokin <oleg.drokin@intel.com>
Tue, 24 Jan 2017 05:24:11 +0000 (05:24 +0000)
commitcffd726304667ea3d84b4b3c1a9b66565e5a5566
treed4a5376387cbfec32d6bc7c4a29f070dd2601061
parenta6e430e81669a6ab40ecae9b416dd2cdee45908c
LU-8929 lfsck: dumper gets current position properly

It is normal that the LFSCK iteration has been done when the
dump hanlder found the status as LS_SCANNING_PHASE1, it may
because of race, or the LFSCK failed to update the status.
Under such cases, the dump handler will use the position in
the last checkpoint as the current position. It may be not
100% accurate, but not serious issue.

Signed-off-by: Fan Yong <fan.yong@intel.com>
Change-Id: I672258baa9d0b0aa8ec12249c13b2b147a274ab4
Reviewed-on: https://review.whamcloud.com/24869
Tested-by: Jenkins
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Lai Siyao <lai.siyao@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
lustre/lfsck/lfsck_layout.c
lustre/lfsck/lfsck_namespace.c