Whamcloud - gitweb
LU-8472 scrub: try to avoid recovery during OI scrub 18/21918/4
authorFan Yong <fan.yong@intel.com>
Tue, 21 Jun 2016 19:12:26 +0000 (03:12 +0800)
committerOleg Drokin <oleg.drokin@intel.com>
Mon, 26 Sep 2016 15:19:10 +0000 (15:19 +0000)
commita41c6fad4672a60166088b9ad8aeb4f1b51c38e7
tree6d9a0bd0f96f6a3bf2b0fbf3371a99287d5ab9b1
parentfdda2ad13bf014ec7e492bda3b8276dfd85fcd6d
LU-8472 scrub: try to avoid recovery during OI scrub

It is known issue that FID based operation will hit -EINPROGRESS
or -EREMCHG failure if related OI mapping is invalid (most cases
because file-level backup/restore).

On the other hand, the recovery for cross-MDTs modifications will
trigger FID based operation(s) before OI scrub rebuilding related
OI mappings.

So during sanity-scrub tests, the scripts should avoid cross-MDTs
recovery via sync all transactions before file-level backup.

More warning message about the recovery failure if because of bad
OI mappings.

Another fix is about setting LOC_F_NEW flag for the object to be
created via out_create().

Test-Parameters: mdtfilesystemtype=ldiskfs mdsfilesystemtype=ldiskfs ostfilesystemtype=ldiskfs mdscount=2 mdtcount=4 testlist=sanity-scrub,sanity-scrub,sanity-scrub
Signed-off-by: Fan Yong <fan.yong@intel.com>
Change-Id: I6e8bc9c5d587be72ecd7e33fa7e9959fe5b34006
Reviewed-on: http://review.whamcloud.com/21918
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
lustre/target/out_handler.c
lustre/target/update_recovery.c
lustre/tests/sanity-scrub.sh