Whamcloud - gitweb
LU-7429 tests: generate dangling name entry properly 63/24763/2
authorFan Yong <fan.yong@intel.com>
Sun, 25 Sep 2016 00:24:10 +0000 (08:24 +0800)
committerOleg Drokin <oleg.drokin@intel.com>
Tue, 24 Jan 2017 05:23:54 +0000 (05:23 +0000)
commitd3919b209e0a4762540d9c28dd6bc6e3c4bbf33b
treecaa71e3881d47c702a85b019dab6fbef28c0edc8
parent6df68292ed6bbcd75811fda0f468dc65bf454256
LU-7429 tests: generate dangling name entry properly

There may be some creation after the dangling injection, such as
create ".lustre/lost+found/MDTxxxx" for LFSCK, create some quota
related local files. These creations may reuse the just released
local object/inode that is referenced by the dangling name entry.
That will fail the dangling injection as to the subsequent LFSCK
will not find dangling name entry. So before deleting the target
object for the dangling name entry, remove some other objects to
avoid the target object being reused by some potential creations.

Signed-off-by: Fan Yong <fan.yong@intel.com>
Change-Id: I0e1bb60c1095119e10009fe2a8ce38687e3e7692
Reviewed-on: https://review.whamcloud.com/24763
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Reviewed-by: Lai Siyao <lai.siyao@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
lustre/tests/sanity-lfsck.sh