== sanity-lfsck test 23c: LFSCK can repair dangling name entry (3) ========================================================== 04:58:37 (1713257917)
#####
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.
#####
debug=-1
debug_mb=150
debug=-1
debug_mb=150
parent_fid=[0x200004a53:0x7c:0x0]
total: 10 open/close in 0.06 seconds: 171.28 ops/second
debug=super ioctl neterror warning dlmtrace error emerg ha rpctrace vfstrace config console lfsck
debug=super ioctl neterror warning dlmtrace error emerg ha rpctrace vfstrace config console lfsck
f0_fid=[0x200004a53:0x87:0x0]
f1_fid=[0x200004a53:0x88:0x0]
Inject failure stub on MDT0 to simulate dangling name entry
fail_val=0x88
fail_loc=0x1621
fail_val=0
fail_loc=0
 - unlinked 0 (time 1713257919 ; total 0 ; last 0)
total: 10 unlinks in 0 seconds: inf unlinks/second
'ls' should fail because of dangling name entry
fail_val=10
fail_loc=0x1602
Trigger namespace LFSCK to find out dangling name entry
Started LFSCK on the device lustre-MDT0000: scrub namespace
fail_val=0
fail_loc=0
debug_mb=8
debug_mb=8