== sanity-lfsck test 18h: LFSCK can repair crashed PFL extent range ========================================================== 05:11:10 (1713345070)
#####
The PFL extent crashed. During the first cycle LFSCK scanning,
the layout LFSCK will keep the bad PFL file(s) there without
scanning its OST-object(s). Then in the second stage scanning,
the OST will return related OST-object(s) to the MDT as orphan.
And then the LFSCK on the MDT can rebuild the PFL extent with
the 'orphan(s)' stripe information.
#####
0+1 records in
0+1 records out
291280 bytes (291 kB) copied, 0.00260717 s, 112 MB/s
Inject failure stub to simulate bad PFL extent range
fail_loc=0x162f
fail_loc=0
dd: error writing '/mnt/lustre/d18h.sanity-lfsck/f0': No data available
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.0039594 s, 0.0 kB/s
Trigger layout LFSCK to find out the bad lmm_oi and fix them
Started LFSCK on the device lustre-MDT0000: scrub layout
Data in /mnt/lustre/d18h.sanity-lfsck/f0 should not be broken
Write should succeed after LFSCK repairing the bad PFL range
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00798271 s, 131 MB/s