== sanity-lfsck test 18h: LFSCK can repair crashed PFL extent range ========================================================== 16:23:47 (1785788627)
#####
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
316748 bytes (317 kB, 309 KiB) copied, 0.0076206 s, 41.6 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 copied, 0.00436216 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
 sanity-lfsck test_18h: @@@@@@ FAIL: (5) Fail to repair crashed PFL range: 3 
  Trace dump:
  = /home/green/git/lustre-release/lustre/tests/test-framework.sh:7477:error()
  = /home/green/git/lustre-release/lustre/tests/sanity-lfsck.sh:3073:test_18h()
  = /home/green/git/lustre-release/lustre/tests/test-framework.sh:7854:run_one()
  = /home/green/git/lustre-release/lustre/tests/test-framework.sh:7917:run_one_logged()
  = /home/green/git/lustre-release/lustre/tests/test-framework.sh:7731:run_test()
  = /home/green/git/lustre-release/lustre/tests/sanity-lfsck.sh:3083:main()
Dumping lctl log to /tmp/testlogs//sanity-lfsck.test_18h.*.1785788632.log
rsync: chown "/tmp/testlogs/.sanity-lfsck.test_18h.debug_log.oleg657-server.1785788632.log.n9H9Nj" failed: Operation not permitted (1)
rsync: chown "/tmp/testlogs/.sanity-lfsck.test_18h.dmesg.oleg657-server.1785788632.log.sr7zY7" failed: Operation not permitted (1)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1668) [generator=3.1.3]