[LU-7217] sanity-lfsck test_23b hangs on START_NAMESPACE

• Type: Bug
• Resolution: Not a Bug
• Priority: Minor
• Affects Version/s: Lustre 2.8.0
• Severity: 3
• Assignee: nasf (Inactive)
• Reporter: parinay v kondekar (Inactive)

Description

Configuration : 4 node setup : 1 MDS/ 1 OSS/ 2 clients
Release
Server 2.7.60
Client 2.7.60

stdout.log
Total allocated inode limit: 0, total allocated block limit: 0

== sanity-lfsck test 23c: LFSCK can repair dangling name entry (3) == 08:02:38 (1443427358)
#####
The objectA has multiple hard links, one of them corresponding
to the name entry_B. But there is something wrong for the name
entry_B and cause entry_B to references non-exist object_C.
In the first-stage scanning, the LFSCK will think the entry_B
as dangling, and re-create the lost object_C. And then others
modified the re-created object_C. When the LFSCK comes to the
second-stage scanning, it will find that the former re-creating
object_C maybe wrong and try to replace the object_C with the
real object_A. But because object_C has been modified, so the
LFSCK cannot replace it.
#####
Inject failure stub on MDT0 to simulate dangling name entry
fail_loc=0x1621
fail_loc=0
'ls' should fail because of dangling name entry
fail_val=10
fail_loc=0x1602
Trigger namespace LFSCK to find out dangling name entry