Whamcloud - gitweb
LU-8218 osd: handle stale OI mapping for non-restore case 59/20659/8
authorFan Yong <fan.yong@intel.com>
Fri, 13 May 2016 15:44:20 +0000 (23:44 +0800)
committerOleg Drokin <oleg.drokin@intel.com>
Thu, 22 Sep 2016 03:04:29 +0000 (03:04 +0000)
commitcecde8bdb4913fd4405d425b0bf3aead03181e9d
tree945940d2d7f49e69ccf6df1ad79751732d7df7a6
parent86e61f80cf6921b537a465b2f6b28914eaac8168
LU-8218 osd: handle stale OI mapping for non-restore case

Sometimes, the user may removes the MDT-object under ldiskfs mode
directly but leaves related OI mapping there. Such case also can
happen if the MDT-object lost because of disk corruption. Under
such case, the OSD ldiskfs should has the ability to distinguish
it from the case of MDT file-level backup/restore; otherwise, the
up layer user will get -EREMCHG (78) when locating such MDT-object
with the FID.

Signed-off-by: Fan Yong <fan.yong@intel.com>
Change-Id: Iede2542968c21755158637089d20a694f12b309e
Reviewed-on: http://review.whamcloud.com/20659
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/include/obd_support.h
lustre/lod/lod_object.c
lustre/osd-ldiskfs/osd_handler.c
lustre/tests/sanity-lfsck.sh