Whamcloud - gitweb
LU-12674 osp: handle -EINPROGRESS on llog objects 48/36348/2
authorAlexey Zhuravlev <bzzz@whamcloud.com>
Wed, 21 Aug 2019 08:32:56 +0000 (11:32 +0300)
committerOleg Drokin <green@whamcloud.com>
Thu, 21 Nov 2019 07:31:54 +0000 (07:31 +0000)
commitf0cf4dfa339f0252cda73f57fe833012c3aea4fa
treeac9d466cd0abe19febac406e6a5539b08e3fa575
parent6a806133a3a53987dbd9c207e0ed82dcd4035bbd
LU-12674 osp: handle -EINPROGRESS on llog objects

if llog object is corrupted and OI doesn't allow access to that
OSP panics being asked to declare new llog record (e.g. for unlink).
Instead OSP should complain in the logs, skip llogging and suggest
to run LFSCK to fix orphans.

Lustre-change: https://review.whamcloud.com/35844
Lustre-commit: a3ec8ff69fceb53a467a80c2e6008869f25f72b4

Signed-off-by: Alex Zhuravlev <bzzz@whamcloud.com>
Change-Id: I18d4d68811833c08cdc1937d147ac6e8c3408a30
Reviewed-by: Mike Pershin <mpershin@whamcloud.com>
Reviewed-by: Lai Siyao <lai.siyao@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
Signed-off-by: Minh Diep <mdiep@whamcloud.com>
Reviewed-on: https://review.whamcloud.com/36348
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
lustre/include/obd_support.h
lustre/osp/osp_sync.c
lustre/tests/sanity.sh