xfs_repair does not seem to work it out. Any suggestions on how to move forward? What options would be useful here?
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
ignored because the -n option was used. Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
data fork in ino 1073741953 claims free block 300776786
data fork in ino 1073741953 claims free block 301055346
data fork in ino 1073741953 claims free block 301055348
data fork in ino 1073741953 claims free block 304081467
data fork in ino 1073741953 claims free block 304081477
data fork in ino 1073741953 claims free block 304081479
data fork in ino 1073741953 claims free block 304081496
data fork in ino 1073741953 claims free block 304081683
data fork in ino 1073741953 claims free block 304081692
data fork in ino 1073741953 claims free block 136792407
data fork in ino 1073741953 claims free block 135861395
data fork in ino 1073741953 claims free block 135855666
data fork in ino 1073741953 claims free block 135857768
data fork in ino 1073741953 claims free block 135857787
data fork in ino 1073741953 claims free block 135857753
data fork in ino 1073741953 claims free block 135857811
data fork in ino 1073741953 claims free block 135853331
data fork in ino 1073741953 claims free block 135858278
data fork in ino 1073741953 claims free block 135862823
data fork in ino 1073741953 claims free block 135861689
data fork in ino 1073741953 claims free block 135862322
data fork in ino 1073741953 claims free block 136065710
data fork in ino 1073741953 claims free block 135862900
data fork in ino 1073741953 claims free block 135932088
data fork in ino 1073741953 claims free block 135864090
data fork in ino 1073741953 claims free block 135864445
data fork in ino 1073741953 claims free block 135855564
data fork in ino 1073741953 claims free block 135864784
data fork in ino 1073741953 claims free block 135865045
data fork in ino 1073741953 claims free block 135851372
data fork in ino 1073741953 claims free block 135865365
data fork in ino 1073741953 claims free block 135865802
data fork in ino 1073741953 claims free block 135865805
data fork in ino 1073741953 claims free block 135865808
data fork in ino 1073741953 claims free block 135865811
data fork in ino 1073741953 claims free block 135865814
data fork in ino 1073741953 claims free block 135865816
data fork in ino 1073741953 claims free block 135865825
data fork in ino 1073741953 claims free block 135865833
data fork in ino 1073741953 claims free block 135865329
data fork in ino 1073741953 claims free block 135866011
data fork in ino 1073741953 claims free block 135866017
data fork in ino 1073741953 claims free block 135866020
data fork in ino 1073741953 claims free block 135867283
data fork in ino 1073741953 claims free block 135867286
data fork in ino 1073741953 claims free block 135867288
out-of-order bmap key (file offset) in inode 1073741953, data fork, fsbno 135867306
bad data fork in inode 1073741953
would have cleared inode 1073741953
- agno = 2
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 3
- agno = 2
- agno = 1
entry "docker.img" in shortform directory 1073741952 references free inode 1073741953
would have junked entry "docker.img" in directory inode 1073741952
out-of-order bmap key (file offset) in inode 1073741953, data fork, fsbno 135867306
would have cleared inode 1073741953
xfs_repair: rmap.c:1279: fix_inode_reflink_flags: Assertion `(irec->ino_is_rl & irec->ir_free) == 0' failed.
Missing reference count record for (2/32341329) len 1 count 2