Whamcloud - gitweb
LU-12674 osp: handle -EINPROGRESS on llog objects 44/35844/4
authorAlexey Zhuravlev <bzzz@whamcloud.com>
Wed, 21 Aug 2019 08:32:56 +0000 (11:32 +0300)
committerOleg Drokin <green@whamcloud.com>
Sat, 7 Sep 2019 01:53:15 +0000 (01:53 +0000)
commita3ec8ff69fceb53a467a80c2e6008869f25f72b4
tree5c2988d0abece8b574bb2ae05f62df29d8d6312d
parent9d5d2714c074a51c9a348b917f3cf32c5005b3b8
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.

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