Whamcloud - gitweb
LU-2657 recovery: don't delete objects
authorNiu Yawei <niu@whamcloud.com>
Mon, 21 Jan 2013 09:13:19 +0000 (04:13 -0500)
committerJohann Lombardi <johann.lombardi@intel.com>
Mon, 18 Feb 2013 13:05:22 +0000 (08:05 -0500)
commit8add7b00d42ec5b5b366063c5634ec7a9ea059da
treec181ff86babf5f1f8ed7f505c14ced9d31cca644
parentb691fbc492b92576088d545785c339a941f52140
LU-2657 recovery: don't delete objects

In mds_lov_update_objids(), when an data object id gap is
detected during recovery, it'll delete all the objects in
the gap, which isn't quite correct, because we can't guarantee
that the id is always increased by the transno order,
furthermore, that could also bring big trouble when the
lov_objid file was removed manually (to rebuild the corrupted
lov_objid file).

Fix type defect in filter_recov_log_unlink_cb(), where
oa->o_id should be increased by each loop cycle.

Signed-off-by: Niu Yawei <yawei.niu@intel.com>
Change-Id: I47247a584da10b1434bf7cb24f606073c6afa903
Reviewed-on: http://review.whamcloud.com/5137
Tested-by: Hudson
Tested-by: Maloo <whamcloud.maloo@gmail.com>
Reviewed-by: Mike Pershin <mike.pershin@intel.com>
Reviewed-by: Johann Lombardi <johann.lombardi@intel.com>
lustre/mds/mds_lov.c
lustre/obdfilter/filter_log.c