== sanity-lfsck test 31a: The LFSCK can find/repair the name entry with bad name hash (1) ========================================================== 05:06:10 (1713431170)
#####
For the name entry under a striped directory, if the name
hash does not match the shard, then the LFSCK will repair
the bad name entry
#####
Inject failure stub on client to simulate the case that
some name entry should be inserted into other non-first
shard, but inserted into the first shard by wrong
fail_loc=0x1628
fail_val=0
total: 2 mkdir in 0.01 seconds: 202.39 ops/second
fail_loc=0
fail_val=0
Trigger namespace LFSCK to repair bad name hash
Started LFSCK on the device lustre-MDT0000: scrub namespace
192.168.204.113@tcp:/lustre /mnt/lustre lustre rw,checksum,flock,user_xattr,lruresize,lazystatfs,nouser_fid2path,verbose,noencrypt,statfs_project 0 0
Stopping client oleg413-client.virtnet /mnt/lustre (opts:)
Starting client: oleg413-client.virtnet:  -o user_xattr,flock oleg413-server@tcp:/lustre /mnt/lustre
  File: '/mnt/lustre/d31a.sanity-lfsck/striped_dir/d0'
  Size: 4096      	Blocks: 8          IO Block: 1048576 directory
Device: 2c54f966h/743766374d	Inode: 144115339490230275  Links: 2
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-04-18 05:06:10.000000000 -0400
Modify: 2024-04-18 05:06:10.000000000 -0400
Change: 2024-04-18 05:06:10.000000000 -0400
 Birth: -
  File: '/mnt/lustre/d31a.sanity-lfsck/striped_dir/d1'
  Size: 4096      	Blocks: 8          IO Block: 1048576 directory
Device: 2c54f966h/743766374d	Inode: 144115339490230276  Links: 2
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-04-18 05:06:10.000000000 -0400
Modify: 2024-04-18 05:06:10.000000000 -0400
Change: 2024-04-18 05:06:10.000000000 -0400
 Birth: -