[LU-966] post-fsck MDS LBUG during recovery due to missing FID

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.2.0, Lustre 2.1.1
• Affects Version/s: Lustre 2.0.0
• Severity: 3
• Assignee: Zhenyu Xu
• Reporter: Alexandre Louvet (Inactive)

Description

We already got this LBUG twice :
================================
ASSERTION(mdd_object_exists(obj)) failed: FID is [0x20001a604:0xc9:0x0]
LustreError: 34372:0:(mdd_object.c:91:mdd_la_get()) LBUG
================================

It always occured after a MDS crash, shine fsck, shine start and during the Clients recovery timeframe.
Each time we achieved to restart the MDT/MDS using abort_recovery.

If we assume that the concerned+missing FID has been destroyed during the fsck on the MDT after a MDS crash for any other problem, and if we consider that there are no other possible scenario than such "external" action to lead to this situation (my opinion, but what do you think ??), can we think about to replace this Assert/LBUG with only a Warning message (at least during Client-recovery phase ...) ???

Issue Links

• is duplicated by: LU-1098 Object doesn't exist!
• is related to: LU-1060 Test failure on test suite replay-vbr, subtest test_7c
• Trackbacks: Changelog 2.1 Changes from version 2.1.0 to version 2.1.1 Server support for kernels: 2.6.18274.12.1.el5 (RHEL5) 2.6.32220.el6 (RHEL6) Client support for unpatched kernels: 2.6.18274.12.1.el5 (RHEL5) 2.6.32220.el6 (RHEL6) 2.6.32.360....
• Trackbacks: Changelog 2.2 version 2.2.0 Support for networks: o2iblnd OFED 1.5.4 Server support for kernels: 2.6.32220.4.2.el6 (RHEL6) Client support for unpatched kernels: 2.6.18274.18.1.el5 (RHEL5) 2.6.32220.4.2.el6 (RHEL6) 2.6.32.360....